Verified:GitHub

threat-model

Define system scope, assets, entry points, and STRIDE threats for a threat model document.

3|Updated Mar 4, 2026

Search Tags:#risk-assessment #threat-modeling #stride #data-flow #security-architecture #attack-surface #threat-documentation

Ready to run

npx skills add https://github.com/jwm-axoni/auggie-pai --skill threat-model-jwm-axoni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: threat-model
Source: https://github.com/jwm-axoni/auggie-pai/tree/main/skills/threat-model
Command: npx skills add https://github.com/jwm-axoni/auggie-pai --skill threat-model-jwm-axoni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling helps identify, document, and mitigate security risks early in the system design by providing a repeatable STRIDE-based approach to asset discovery, entry-point mapping, and risk prioritization.

Core Features & Use Cases

Systematic STRIDE enumeration for assets, entry points, data flows, and trust boundaries.
Generates formal threat model documents with data flow diagrams and risk matrices.
Supports architecture reviews, threat analysis, and risk-based remediation planning.

Quick Start

Define the system scope and assets, then run threat-model to generate a complete STRIDE-based threat model document.

Frequently Asked Questions about threat-model

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

FAQPage Schema

What is STRIDE threat modeling and when should I apply it to my system architecture?▼

STRIDE threat modeling systematically identifies security risks by categorizing threats into Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege. Apply it during system design and architecture reviews to map data flows and prioritize risk remediation.

How do I document data flow diagrams and trust boundaries for a security architecture review?▼

Document data flow diagrams and trust boundaries by defining system scope, identifying critical assets and entry points, mapping data flows, and establishing trust boundaries. This process generates a formal threat model document detailing risk matrices and remediation plans.

Can I use this threat modeling approach for both software applications and infrastructure components?▼

Yes, this threat modeling approach applies to both software applications and infrastructure components. It supports risk-based threat analysis across diverse systems by mapping assets, entry points, and data flows to generate comprehensive security assessment documentation.

How do I prioritize security risks after enumerating STRIDE threats for my system's entry points?▼

Prioritize security risks after enumerating STRIDE threats by applying risk scoring to identified vulnerabilities across assets and entry points. This generates a structured risk matrix within the threat model document, enabling targeted risk-based remediation planning.

Does threat-model require any specific security tools or dependencies to generate a threat model document?▼

No, threat-model does not require any specific security tools or external dependencies to generate a threat model document. You only need to define your system scope and assets to produce the formal STRIDE-based analysis with data flow diagrams and risk matrices.