threat-modeling

Automate STRIDE threat modeling to enumerate assets, map trust boundaries, and suggest mitigations.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/nist0/CoDev --skill threat-modeling-nist0
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: threat-modeling
Source: https://github.com/nist0/CoDev/tree/main/.github/skills/threat-modeling
Command: npx skills add https://github.com/nist0/CoDev --skill threat-modeling-nist0

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive and systematic approach to threat modeling, helping you identify and mitigate potential security risks in your systems.

Core Features & Use Cases

  • System Asset Enumeration: Lists all significant assets in a system before any threat analysis.
  • Trust Boundary Mapping: Identifies and documents trust boundaries and the data crossing them.
  • STRIDE Analysis: Evaluates all six STRIDE categories (Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, Elevation of Privilege) for every trust boundary.
  • Threat Scoring: Scores threats on a likelihood × impact matrix.
  • Mitigation Selection: Suggests specific mitigations for high or critical threats.
  • Residual Risk Statement: Documents residual risk and reasons for accepting it.
  • Output Artifact: Generates a threat register table as the final deliverable.

Quick Start

Run the threat-modeling skill with the system description and trust boundaries you want to analyze.

Frequently Asked Questions about threat-modeling

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

FAQPage Schema
How do I automate STRIDE threat modeling for my software system?▼

You can automate STRIDE threat modeling by inputting your system details and trust boundaries to systematically enumerate assets, analyze threats across all six categories, and generate a threat register table.

What is the best way to map trust boundaries during security risk analysis?▼

Mapping trust boundaries during security risk analysis involves identifying and documenting the distinct trust levels within your system architecture and cataloging the data that crosses each boundary.

How do I score and prioritize security threats identified during threat modeling?▼

Threat modeling scores security risks by evaluating each identified threat using a likelihood and impact matrix, allowing you to prioritize and select specific mitigations for high or critical threats.

Can I generate a threat register table automatically from a system description?▼

Yes, you can generate a threat register table automatically by running a threat modeling analysis on your system description, which outputs the final deliverable along with a residual risk statement.

Does threat modeling require manual input for trust boundaries and system assets?▼

Yes, threat modeling requires manual input of system details and trust boundaries to accurately enumerate assets and evaluate potential security risks before suggesting mitigations.

When should I document residual risk in my threat modeling process?▼

You should document residual risk in your threat modeling process after selecting specific mitigations for high or critical threats, providing clear reasons for accepting any remaining security risks.