security-threat-model

Threat modeling a microservice involves mapping trust boundaries, data exfiltration paths, and attacker capabilities. This Skill automates that AppSec analysis directly from repository code, producing a Markdown threat model highlighting critical risks and hardening steps for new services.

Abuse path enumeration is the process of identifying and prioritizing realistic attack scenarios within a codebase. This Skill performs abuse path enumeration by mapping attacker capabilities against trust boundaries and assets, outputting prioritized security risks and concrete mitigation recommendations.

Yes, you can generate a threat model for a specific directory by directing the analysis to target that path. The Skill scopes its repository-grounded assessment, enumerating assets and abuse paths exclusively within the specified directory to provide concise and relevant security findings.

No, this Skill does not provide general architecture summaries. It is triggered exclusively by explicit requests for codebase threat modeling, abuse path enumeration, or AppSec risk assessment, avoiding non-security design work to focus strictly on identifying vulnerabilities and mitigations.

The threat model output is a concise Markdown document. It systematically details identified trust boundaries, assets, attacker capabilities, abuse paths, and suggested security controls, providing a structured format for security engineers to review and implement mitigations.

The best way to enumerate attack scenarios is to map attacker capabilities against trust boundaries and assets within the code. This Skill automates that risk assessment, prioritizing realistic abuse paths and suggesting concrete security controls to focus manual review efforts effectively.