security-threat-model

To generate a threat model, trigger the skill by explicitly asking it to threat model a codebase or path, and it will output a concise Markdown document enumerating trust boundaries, assets, and abuse paths.

Repository-grounded threat modeling analyzes actual codebase content to identify specific vulnerabilities and abuse paths, producing concrete mitigations rather than relying on generic security checklists or architecture summaries.

Yes, you can use this AppSec tool to enumerate abuse paths for a microservice by explicitly requesting threat modeling for the specific path, which surfaces attacker capabilities and recommended input validation strategies.

Vulnerability analysis and mitigation recommendations are produced by explicitly requesting AppSec threat modeling on the repository, yielding a Markdown report with concrete security controls and implementation hints.

You should not use this approach for general architecture summaries, non-security design work, or standard code review, as it triggers exclusively for AppSec threat modeling and abuse path enumeration.

No dependencies are required to analyze trust boundaries, as the skill operates directly on the repository content you provide to map assets and attacker capabilities into a Markdown threat model.