security-threat-model

To create a threat model for a repository, you need a structured process that catalogs assets, trust boundaries, and abuse paths. This Skill generates an evidence-backed threat model anchored to exact repo paths and CI/build contexts.

Evidence-based threat modeling in application security grounds risk assessment in actual codebase artifacts. It ties attacker capabilities and abuse paths to exact repository paths and CI contexts to produce an actionable, targeted review document.

To generate a Mermaid diagram for trust boundaries and abuse paths, analyze the repository's architecture and map data flows. This Skill outputs a compact Markdown threat model document that includes a visual Mermaid diagram of these security boundaries.

Yes, you can use repository analysis for AppSec risk prioritization by mapping identified abuse paths to exact code locations. This approach yields a mapped set of risks tailored to the codebase, enabling targeted security reviews and remediation.

This threat modeling approach works without external dependencies, requiring only access to the target codebase. It uses a provided prompt template to analyze repo paths and CI build contexts, producing a standalone Markdown threat model.

The best way to document security mitigations is through a structured Markdown threat model that maps risks to specific repository paths. This Skill produces an evidence-backed document with a Mermaid diagram detailing assets, abuse paths, and mitigations.