threat-model

Generates STRIDE-based threat model documents with risk ratings and mitigation strategies.

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/tektonlabs/ai-software-design --skill threat-model-tektonlabs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-model
Source: https://github.com/tektonlabs/ai-software-design/tree/main/.claude/skills/_deprecated/architecture/threat-model
Command: npx skills add https://github.com/tektonlabs/ai-software-design --skill threat-model-tektonlabs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill addresses the need to systematically identify, analyze, and document security threats before development begins, producing a structured threat model with risk ratings and mitigations. Note: this Skill is deprecated and its content is now consolidated into Section 9 (Security Architecture) of the Software Architecture Document skill. ## Core Features & Use Cases - STRIDE Threat Analysis: Catalogs threats across Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege categories. - Risk Assessment: Scores threats using likelihood and impact matrices, producing a prioritized threat list and heat map. - Mitigation & Compliance Mapping: Defines mitigation strategies, security controls, and compliance mappings (GDPR, PCI-DSS, SOC 2) with sign-off workflows. - Use Case: A security architect documenting threats for a new web application would normally use this to produce a threat model and threat register, but should now use the Software Architecture Document skill instead. ## Quick Start Ask the agent to generate the Software Architecture Document for your system, since threat model content now lives in Section 9 of that document.

Frequently Asked Questions about threat-model

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

FAQPage Schema
How do I create a threat model using STRIDE methodology?▼

STRIDE threat modeling catalogs threats across six categories: Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. Each threat is rated by likelihood and impact, then mapped to mitigations and security controls.

Is the threat-model skill still active in this SDLC workflow?▼

No, this skill is deprecated. Threat model content is now consolidated into Section 9 (Security Architecture) of the Software Architecture Document skill, and users are redirected there if this skill is invoked.

What inputs are required to generate a threat model?▼

The skill requires an architecture design document, C4 diagrams, a data model, and an NFR register with security requirements. Compliance requirements such as GDPR, HIPAA, or PCI-DSS are recommended but optional.

How are security risks scored in a threat model?▼

Risks are scored by multiplying likelihood (1-5) by impact (1-5), producing a risk score visualized on a heat map. Threats are then prioritized, with critical and high risks requiring documented mitigation strategies.

Who must sign off on a threat model document?▼

Required sign-offs include the Security Architect for threat analysis, the Solution Architect for architecture accuracy, and the CISO for risk acceptance. A Compliance Officer sign-off is conditional on regulatory applicability.