security-threat-model

Generate Markdown threat model reports from repository code analysis.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/jacketlong23/skills --skill security-threat-model-jacketlong23
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/jacketlong23/skills/tree/main/security-threat-model
Command: npx skills add https://github.com/jacketlong23/skills --skill security-threat-model-jacketlong23

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of identifying and analyzing security threats within a codebase, helping to proactively secure software by enumerating potential vulnerabilities and suggesting mitigations.

Core Features & Use Cases

  • Repository-Grounded Threat Modeling: Analyzes code repositories to identify trust boundaries, assets, attacker capabilities, and abuse paths.
  • Actionable Security Reports: Generates concise Markdown threat models with prioritized risks and concrete mitigation recommendations.
  • Use Case: A development team is about to deploy a new microservice. They can use this Skill to perform an AppSec-grade threat model on the service's repository, ensuring potential security flaws are identified and addressed before production.

Quick Start

Use the security-threat-model skill to threat model the codebase located at '/path/to/my/project'.

Frequently Asked Questions about security-threat-model

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I perform threat modeling on a codebase repository?

To perform threat modeling on a codebase, analyze the repository to identify trust boundaries, assets, attacker capabilities, and abuse paths, then generate a Markdown report with prioritized risks and mitigations.

What is repository-grounded threat modeling and how does it identify abuse paths?

Repository-grounded threat modeling analyzes source code directly to discover trust boundaries, assets, and attacker capabilities, mapping these to specific abuse paths and suggesting concrete mitigations in a concise report.

Can I use this for AppSec design work on a new microservice?

Yes, you can use this for AppSec design work on a new microservice by enumerating potential security flaws, analyzing attacker capabilities, and addressing abuse paths before production deployment.

What's the best way to enumerate security threats and risks in source code?

The best way to enumerate security threats in source code is to analyze the repository to identify assets and trust boundaries, map potential abuse paths, and generate a Markdown report with prioritized mitigations.

Does this threat model analysis work for general architecture summaries?

No, this threat model analysis does not work for general architecture summaries or non-security design tasks; it is explicitly triggered only for security threat modeling, abuse path analysis, and AppSec design work.