Ability design

I'm working on a project rpg like action game that has a lot of different character abilities(read: attacks, spells, heals, and such). So I'm just wondering if there is a preferred way of doing this, or even an optimal way.

Currently I'm creating a main ability behavior that handles input from the player or AI controller. This behavior creates different behaviors to judge different condition(such as target health, your health, target range). It also creates different behaviors to handle the individual activated portions(such as deal damage to target or buffing the target) and passive portions(such as increasing a character stat while they have the ability loaded in). I've been doing this to save time having to code the same parts of an ability over and over.

This means the same character can have a different instance of the same behavior for each ability, which quickly adds up. This has been working on a small scale, but I'm wondering if having this many behaviors will be a problem later. I mean I'm pretty close to where I want my game scale to be and it runs fine on the hunk of junk that I call my laptop, but I'd still be interested to know if there is a better way of doing this.

Also, I'm wondering if there is an easier way to create an instance of a behavior with a behavior onAdd(). I'm currently using a funky string variable setup to get it to work now. Basically, I have strings in the main ability behavior called Conditions/Passives/Actives. Each string has TAB separated sections for each behavior to create/add when this behavior is added to an Object. The first word in the field is a BehaviorTemplate name and the rest are its variables. So it'd be something like:

%conditions = "rangeCondition 10" TAB "healthPercentCondition 0 25" TAB "targetTypeCondition friendly self";

%x = getFieldCount(%conditions);
for(%y = 0; %y != %x; %y++) {
%field = getField(%conditions, %y);

%template = getWord(%field, 0);
%instance = %template.createInstance();

%values = removeWord(%field, 0);

%instance.setVariables(%values);

%this.owner.addBehavior(%instance);
}

the new behaviors would know what to do with %values, or they would echo an error if they were sent the wrong things.

Sorry for the long post. Just don't want to spend my time doing something that's just going to cause a problem.
Thanks in advance for any help you might have.

--Edit--

Opps actually solved it right after I finished typing it. I think I just need to think through the possess I was using.

I'm just going to create a single instance of the sub behaviors if they doesn't already exist when the ability is added. then pass the values to the instance when it tests the conditions, activates, or whatever. Might even just add the instance to the scene instead of an individual object too.