What problem does it solve?
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Core Features & Use Cases
- Anchor architectural claims to evidence in the repository (paths, files, and config snippets).
- Enumerate trust boundaries, assets, attacker capabilities, and abuse paths with evidence-backed claims.
- Produce a prioritized threat model with likelihood/impact reasoning and concrete mitigations.
- Generate a compact Mermaid diagram illustrating components and trust boundaries.
- Provide a structured output suitable for review and follow-up actions.
Quick Start
Prompt the user to request a threat model for a given repo path, then execute the workflow to produce a repository-focused threat model grounded in repo evidence.