security-threat-model

Provide the repo path and any known context such as deployment model and internet exposure. The Skill maps components, trust boundaries, and entry points from code evidence, then enumerates prioritized threats and writes a Markdown report named after the repository.

The report contains an executive summary, scope and assumptions, a system model with a Mermaid diagram, an assets table, an attacker model, abuse paths, a threat table with likelihood and impact, criticality calibration, and focus paths for manual security review.

Use this Skill only for explicit threat-modeling requests, not general architecture analysis or code review. It focuses on attacker goals, abuse paths, and risk prioritization rather than finding individual bugs or style issues.

Yes. Before producing the final report, the Skill summarizes key assumptions and asks one to three targeted questions about deployment, exposure, and data sensitivity. If you cannot answer, it proceeds with explicit assumptions and marks conditional conclusions.

Each threat receives qualitative likelihood and impact ratings (low, medium, high) with short justifications, combined into a priority of critical, high, medium, or low. Existing controls found in the repo adjust the ranking, and the assumptions influencing it are stated.