security-threat-model

Generate a threat model by pointing the skill at your repository path to enumerate trust boundaries, assets, attacker capabilities, and abuse paths. The skill requires explicit evidence anchors from the repository content to ground the analysis and identify potential security risks.

Repository-grounded threat modeling is an AppSec process that analyzes actual source code to identify security threats. It enumerates trust boundaries and abuse paths while requiring explicit evidence anchors from the repository, ensuring the threat model reflects the real codebase architecture.

Yes, you can use this skill for security design reviews of new features by targeting the associated codebase path. It identifies threats and abuse paths early in the development lifecycle, assigning likelihood, impact, and priority to each identified risk with clear justifications.

Security risks are prioritized by assigning likelihood, impact, and priority levels to identified threats. The skill provides clear justifications for each risk assessment based on the enumerated attacker capabilities and abuse paths found within the repository's trust boundaries.

No, the skill requires explicit evidence anchors from the repository to generate accurate threat models. It follows a structured workflow that grounds the analysis in actual codebase content, ensuring the identified trust boundaries and abuse paths are verifiable.

The best way to identify abuse paths is through automated threat enumeration based on repository content. The skill maps attacker capabilities against trust boundaries and assets within the codebase, generating a structured analysis of potential abuse paths and corresponding mitigations.