What problem does it solve?
This Skill helps you uncover how a design can be abused, bypassed, confused, or quietly gamed before it ships. It is especially useful when normal happy-path reviews miss trust boundaries, malicious actors, prompt injection risks, or incentive-driven misuse.
Core Features & Use Cases
- Boundary-Centered Threat Modeling: Maps assets, trust boundaries, actors, and invariants so you can see where security and correctness actually change hands.
- Abuse Case Generation: Uses STRIDE, LLM-specific attack patterns, and incentive failure modes to produce concrete attack scenarios instead of vague warnings.
- Risk Ranking and Mitigation Design: Prioritizes issues by impact and feasibility, then recommends boundary-level controls, tests, and telemetry.
- Use Cases: Review authentication flows, plugin systems, tool-calling agents, APIs, secret handling, untrusted file or network inputs, and metrics that could be gamed.
Quick Start
Ask the adversarial-design-review skill to assess your API, CLI, agent, or plugin design by identifying trust boundaries, abuse cases, top-ranked risks, and concrete mitigations.