security-threat-model

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

Updated Jul 17, 2026
One-click install
npx skills add https://github.com/guneysol/agent-configs --skill security-threat-model-guneysol
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/guneysol/agent-configs/tree/main/agents/skills/security-threat-model
Command: npx skills add https://github.com/guneysol/agent-configs --skill security-threat-model-guneysol

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security teams often produce generic threat model 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: Generates abuse paths with qualitative likelihood and impact reasoning, producing a threat table with stable IDs (TM-001, etc.) and critical/high/medium/low priorities. - Structured Output Contract: Delivers a Markdown report with an executive summary, Mermaid trust-boundary diagram, threat model table, and focus paths for manual security review. - Use Case: Point the Skill at a web service repository before a launch review; it maps endpoints and data flows, validates assumptions with you, then writes a <repo>-threat-model.md file your AppSec team can act on. ## Quick Start Ask the assistant to threat model this repository and write a prioritized Markdown threat model 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 a 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, validates assumptions with you, then writes a prioritized Markdown threat model file.

What does a repo-grounded threat model include?▼

It includes an executive summary, scope and assumptions, a system model with a Mermaid trust-boundary diagram, an asset table, attacker capabilities, abuse paths, a prioritized threat table, and focus paths for manual security review.

When should I trigger threat modeling versus a code review?▼

Trigger it only when you explicitly want threats, abuse paths, or AppSec threat modeling for a codebase. It is not intended for general architecture summaries, routine code review, or non-security design work.

How are threats prioritized in the threat model?▼

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

Does the threat model handle missing deployment context?▼

Yes. Before finalizing, it summarizes key assumptions and asks one to three targeted questions about deployment model, exposure, and data sensitivity. If unanswered, it proceeds with explicit assumptions and marks conditional conclusions.