ability-analysis

ABILITY_ANALYSIS Skill

Trigger Pattern: Always (Aptos Move) --- foundational security check Inject Into: Breadth agents, depth agents

For every struct defined in the audited modules:

STEP PRIORITY: Steps 2 (Copy Ability Audit) and 6 (Ability Combination Analysis) are where HIGH/CRITICAL severity findings most commonly hide. Do NOT rush these steps. If constrained, skip conditional sections (7) before skipping 2 or 6.

1. Struct Ability Inventory

Enumerate ALL structs defined in the audited modules:

Struct	Module	Abilities	Represents Value?	Represents Obligation?	Is Resource?	Security Assessment
{name}	{module}	copy, drop, store, key	YES/NO	YES/NO	YES/NO	{assessment}

Classification guide:

• Value-bearing: Coins, LP tokens, shares, receipts, vouchers, NFTs --- anything that represents transferable economic value or a claim to value
• Obligation-bearing: Hot potatoes, flash loan receipts, callback obligations, lock receipts --- anything that MUST be consumed before transaction ends
• Resource: Singleton state containers, registries, configuration stores --- things that should exist at most once per address/globally
• Data: Purely informational structs with no security-sensitive lifecycle (events, parameters, intermediate computation results)

For each struct: What abilities does it NEED vs what abilities does it HAVE? Excess abilities are the attack surface.

2. Copy Ability Audit

For each struct with the copy ability:

2a. Value Duplication Check

Struct	Has copy?	Represents Value?	Duplication Exploitable?	Severity
{name}	YES/NO	YES/NO	YES/NO --- {reason}	{H/M/L/N/A}

CRITICAL: copy on a value-bearing type means the value can be duplicated at zero cost. This is the Move equivalent of a double-spend.