security-threat-model

Automate threat modeling by running the skill on your project path, which analyzes the repository to identify trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, then outputs a Markdown threat model document.

Evidence-backed security threat modeling grounds every architectural claim and identified vulnerability in your actual repository content, ensuring precise analysis of trust boundaries and abuse paths rather than relying on generic assumptions.

Security threat modeling works with any codebase structure as long as you provide access to the repository and its source code, allowing the analysis to map specific trust boundaries and assets accurately.

Generate a threat model document by pointing the skill at your project path, which processes the source code to enumerate assets, attacker capabilities, and mitigations, producing a concise Markdown file.

The best way to identify trust boundaries is to use repository-grounded threat modeling, which automatically maps architectural trust zones and assets based on actual source code evidence.

Your threat model may lack specific abuse paths if the analysis is not repository-grounded, whereas evidence-backed repository analysis automatically enumerates precise attacker capabilities and abuse paths from your source code.