security-threat-model

To perform threat modeling on a codebase, this Skill analyzes repository code to enumerate trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, generating a concise Markdown threat model.

Repository-grounded threat modeling anchors all security claims and vulnerability analysis to specific evidence within the codebase, ensuring identified abuse paths and mitigations are accurately traced to actual code.

You can identify abuse paths and attacker capabilities by running this Skill against your current directory, which automatically enumerates security vulnerabilities and trust boundaries from the repository code.

Yes, you can use this proactive AppSec analysis for an existing codebase by triggering it with an explicit request for codebase threat modeling in your current directory.

The best way to document security vulnerabilities and mitigations during code review is to generate a concise Markdown threat model that explicitly maps identified abuse paths to their corresponding security mitigations.

A limitation of this automated vulnerability analysis is that it requires explicit user requests to trigger codebase threat modeling, and it focuses solely on enumerating trust boundaries and abuse paths rather than patching code.