security-threat-model

Generating a threat model for a repository requires analyzing the codebase to enumerate assets, trust boundaries, and abuse paths. This skill outputs an evidence-backed Markdown threat model prioritized by repo-specific risks.

Repository-grounded threat modeling anchors application security risk assessment to actual codebase evidence. It identifies attacker capabilities and mitigations by analyzing explicit assumptions and architectural claims within the project path.

No, you need to supply deployment context and an existing architecture summary as inputs. The threat modeling process uses these alongside repo root scope to generate a concise Markdown threat model anchored to evidence.

To identify trust boundaries and abuse paths, you must analyze the repo structure and deployment context. This skill enumerates components and attacker capabilities to document these security boundaries in a Markdown model.

The best way to document mitigations is generating a concise Markdown threat model that references repo evidence and explicit assumptions. This approach ensures mitigations are prioritized and directly anchored to identified architectural risks.

No, the threat modeling method automatically enumerates components from the specified repository or project path. It processes the repo root scope to map assets and components without requiring manual extraction.