What problem does it solve? Security testers often find isolated weaknesses like an IDOR, SSRF, or leaked token but struggle to determine whether the finding is reportable or how to escalate it into demonstrable impact. This Skill turns a raw primitive into a structured chain card that names the victim, asset, and harm before a report is written. ## Core Features & Use Cases - Chain Card Generation: Produces a standardized card covering primitive, boundary broken, authority upgrade, victim, impact target, current proof, missing proof, and next five pivots. - Chainability Scoring: Applies a 0-5 rubric that separates informational findings from account takeover, privilege escalation, cross-tenant access, and RCE-level impact. - Primitive Pivot Ladders: Provides concrete escalation paths for IDOR, token/secret leaks, SSRF, XSS, race conditions, and import/parser flaws. - Use Case: After discovering a signed URL leak during a bug bounty assessment, invoke the chain mode to validate token scope, trace where it is generated, and chain it toward storage, CI, or cloud access before deciding reportability. ## Quick Start Ask the agent to run attack-chain on your current finding, for example by describing the primitive you found and requesting a chain card with pivot options.
