security-threat-model

To generate a threat model for your codebase, you run the skill with the path to your repository. It analyzes the code to identify trust boundaries, assets, attacker capabilities, abuse paths, and mitigations specific to your project.

Repository-grounded threat modeling analyzes your actual source code to deliver a security assessment specific to your project, rather than applying a generic checklist. It identifies concrete abuse paths and prioritized mitigations based on the code's real trust boundaries.

You perform an AppSec risk assessment by running this skill against your codebase path. It evaluates attacker capabilities and prioritizes realistic attacker goals to produce an AppSec-grade threat model with concrete impacts and mitigations.

No, this threat modeling approach does not use generic security checklists. It is repository-grounded, meaning it prioritizes realistic attacker goals and concrete impacts by analyzing the specific trust boundaries and assets within your codebase.

Yes, you can assess codebase security for a specific project directory by providing its path to the skill. The tool generates a detailed threat model focusing on the trust boundaries and assets found within that specific repository location.