security-threat-model

Threat modeling a repository requires an explicit scope and prompt template to enumerate threats, abuse paths, and mitigations. The Skill anchors its analysis in actual repository evidence, mapping trust boundaries and components to produce prioritized security guidance.

Repository-grounded threat modeling identifies security risks by anchoring analysis in actual codebase evidence. It maps system components, data stores, and trust boundaries to enumerate attacker goals, abuse paths, and targeted mitigations tied to concrete assets and surfaces.

Yes, threat modeling can be applied to specific codebase subpaths. You must explicitly request the threat model for that path and provide the required scope and prompt template to generate evidence-driven security analysis for the targeted application area.

Yes, producing a structured threat model requires explicit scope, repository evidence, and a prompt template. Without these inputs, the analysis cannot enumerate threats, abuse paths, and mitigations with the necessary evidence anchors for prioritized guidance.

The best way to identify trust boundaries and abuse paths in AppSec is using evidence-driven threat modeling. By mapping components and data stores against repository evidence, you can enumerate attacker goals and generate prioritized, actionable mitigations tied to concrete surfaces.

You should not use automated threat modeling when you lack explicit scope or repository evidence. The process requires a prompt template and actual codebase access to anchor threats, abuse paths, and mitigations to real assets and surfaces for accurate risk assessment.