gaia-threat-model

Automate STRIDE and DREAD threat modeling into a validated threat-model document.

2|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-threat-model
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gaia-threat-model
Source: https://github.com/gaiastudio-ai/gaia-public/tree/main/plugins/gaia/skills/gaia-threat-model
Command: npx skills add https://github.com/gaiastudio-ai/gaia-public --skill gaia-threat-model

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Automates collaborative security threat modeling to produce a validated threat-model document that covers asset identification, STRIDE analysis, DREAD scoring, mitigation strategies, and security requirements.

Core Features & Use Cases

  • Collaborative STRIDE analysis for assets and data flows across system components.
  • DREAD-based risk scoring with prioritized mitigations mapped to concrete actions.
  • Generates docs/planning-artifacts/threat-model.md with traceability to architecture documentation.
  • Enforces architecture.md prerequisites and coordinates with the security subagent (Zara) for analysis.

Quick Start

Initiate threat-model generation and review the resulting document at docs/planning-artifacts/threat-model.md

Frequently Asked Questions about gaia-threat-model

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

FAQPage Schema
How do I automate threat modeling for a complex system architecture?

Threat modeling for complex system architectures is automated by identifying assets, applying STRIDE analysis, scoring risks with DREAD, and mapping mitigations to generate a validated security document.

When do I need to use STRIDE and DREAD for security analysis?

STRIDE and DREAD are needed for security analysis when architectural reviews require identifying data flow threats, scoring risk severity, and planning concrete mitigations across system components.

How do I generate a threat model document with risk scoring and mitigations?

Generating a threat model document involves running collaborative STRIDE and DREAD analysis on your architecture to output prioritized risk scores and mitigation strategies to a markdown file.

Do I need an architecture document before starting threat modeling?

An architecture document is required before starting threat modeling because the analysis enforces architecture prerequisites to ensure accurate asset identification and data flow mapping.

What is the best way to prioritize security mitigations after STRIDE analysis?

The best way to prioritize security mitigations after STRIDE analysis is applying DREAD risk scoring to quantify threat severity and map concrete actions to the highest priority vulnerabilities.

Can I trace generated threat model mitigations back to my architecture documentation?

Generated threat models include traceability to architecture documentation, ensuring that identified security requirements and mitigations are directly linked to the analyzed system components.