security-threat-model

Generates repository-grounded threat models with trust boundaries, abuse paths, and prioritized mitigations.

Updated May 11, 2026
One-click install
npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill security-threat-model-cloudofgeorge
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/cloudofgeorge/AI-hands-Engineer/tree/main/skills/engineering/security/security-threat-model
Command: npx skills add https://github.com/cloudofgeorge/AI-hands-Engineer --skill security-threat-model-cloudofgeorge

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security reviews often produce generic checklists disconnected from the actual codebase. This Skill produces an AppSec-grade threat model anchored to real repository evidence, with explicit assumptions, prioritized abuse paths, and concrete mitigations. ## Core Features & Use Cases - Evidence-Anchored Analysis: Enumerates trust boundaries, assets, entry points, and attacker capabilities, with every architectural claim tied to a repo path or symbol. - Prioritized Threat Enumeration: Builds multi-step abuse paths with qualitative likelihood and impact reasoning, producing a stable threat table (TM-001, TM-002, ...) with critical/high/medium/low priorities. - Assumption Validation Workflow: Pauses to confirm deployment model, exposure, and data sensitivity with the user before finalizing the report. - Use Case: Point the Skill at a service repository before a launch review; it maps components and boundaries, renders a Mermaid diagram, and writes a <repo>-threat-model.md report with focus paths for manual security review. ## Quick Start Ask the agent to threat model this repository and produce a prioritized Markdown report with abuse paths and mitigations.

Frequently Asked Questions about security-threat-model

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

FAQPage Schema
How do I create a threat model for an existing codebase?▼

Provide the repository path and any known context such as deployment model and internet exposure. The Skill maps components, trust boundaries, and entry points from repo evidence, then enumerates prioritized abuse paths and writes a Markdown threat model report.

What does a repo-grounded threat model include?▼

It includes a system model with a Mermaid diagram, an asset table, attacker capabilities and non-capabilities, entry points with evidence anchors, 5-10 abuse paths, a threat table with likelihood and impact, and focus paths for manual review.

When should I not use threat modeling on a repository?▼

Skip it for general architecture summaries, routine code review, or non-security design work. The Skill is scoped to explicit AppSec threat modeling requests and deliberately avoids generic checklist output.

How are threats prioritized in the threat model?▼

Each threat gets qualitative likelihood and impact ratings with short justifications, combined into a critical/high/medium/low priority adjusted for existing controls. The Skill states which assumptions most influence the ranking.

Does the threat model require user input before finalizing?▼

Yes. Before writing the final report, the Skill summarizes key assumptions and asks 1-3 targeted questions about deployment model, exposure, authn/authz, and data sensitivity, then waits for confirmation or proceeds with explicit assumptions.