security-threat-model

To generate a threat model from your codebase, trigger the Skill with a request for AppSec design work or abuse path enumeration. It analyzes your repository to enumerate trust boundaries, assets, attacker capabilities, and mitigations.

Abuse path enumeration is the process of identifying concrete sequences of attacker actions and their potential impact within a system. This Skill generates repository-grounded abuse paths to proactively assess application security risks.

You need a repository-grounded threat assessment before deploying new microservices or features to identify potential vulnerabilities early in the development lifecycle and ensure all security controls are properly addressed.

Yes, this threat modeling approach provides actionable advice on both existing and recommended security controls. It identifies concrete mitigation strategies directly related to the abuse paths and vulnerabilities found in your codebase.

No, you cannot use this for general architecture summaries or non-security tasks. It is specifically triggered by explicit requests for threat modeling, abuse path enumeration, and AppSec design work.

The best way to identify trust boundaries and assets is to use a repository-grounded threat model. This approach directly analyzes your codebase to map out attacker capabilities and enumerate system assets accurately.