security-threat-model

Threat modeling from a codebase involves analyzing repository evidence to enumerate trust boundaries, assets, attacker capabilities, and abuse paths. This skill automates that process by generating a concise Markdown threat model with prioritized risks and recommended mitigations.

Repository-grounded threat modeling analyzes actual codebase evidence to identify concrete abuse paths and security impacts, rather than applying generic checklists. It prioritizes realistic attacker goals and produces a prioritized risk assessment tailored to your specific application architecture.

Yes, you can use this for AppSec design reviews on a new microservice. It analyzes the microservice codebase to identify trust boundaries, enumerate potential threats like data exfiltration or privilege escalation, and output a prioritized list of risks and recommended mitigations.

Enumerating abuse paths during a security review requires identifying concrete sequences of attacker actions leading to security incidents. This skill automates abuse path enumeration by analyzing your repository evidence to map attacker capabilities and prioritize realistic attack goals.

No, this threat modeling approach does not require external dependencies or tools to function. It operates directly on your repository evidence using its internal scripts and references to assess risk likelihood, impact, and generate the final Markdown threat model.