threat-model

Generate prioritized STRIDE threat models from existing DFDs.

489|254|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/me2resh/apexyard --skill threat-model-me2resh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: threat-model
Source: https://github.com/me2resh/apexyard/tree/main/.claude/skills/threat-model
Command: npx skills add https://github.com/me2resh/apexyard --skill threat-model-me2resh

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you prevent security regressions by producing a point-in-time STRIDE threat catalogue grounded in your project’s Data Flow Diagram (DFD), including prioritized mitigations.

Core Features & Use Cases

  • DFD-grounded STRIDE walk: Applies Spoofing, Tampering, Repudiation, Information Disclosure, DoS, and EoP to each DFD trust-boundary crossing and entry point.
  • Threat history + trend rendering: Persists a structured audit artefact and renders trends across repeated runs.
  • Threat Dragon export: Optionally emits an OWASP Threat Dragon v2 JSON file for diagrammatic review in Threat Dragon.
  • Security-row escalation: Designed as the expert companion when /launch-check shows WARN or FAIL for the security row.

Quick Start

Run threat-model for your project by invoking /threat-model workspace/<project-path> to generate a prioritized STRIDE threat catalogue (and optionally a Threat Dragon JSON export).

Frequently Asked Questions about threat-model

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

FAQPage Schema
How do I generate a STRIDE threat model from a Data Flow Diagram?

STRIDE threat modeling identifies security risks by systematically applying Spoofing, Tampering, Repudiation, Information Disclosure, Denial of Service, and Elevation of Privilege categories to each entry point and trust-boundary crossing in your architecture. It produces a prioritized catalogue of threats and mitigations.

What is the best way to maintain threat history and audit trends for application security?

Maintaining threat history involves persisting a structured audit artefact after each point-in-time security review, allowing you to render and track threat trends across repeated runs. This helps prevent security regressions by providing consistent enumeration over time.

Can I export STRIDE threat models to OWASP Threat Dragon?

Yes, you can export STRIDE threat models to OWASP Threat Dragon by generating a Threat Dragon v2 JSON file. This optional export allows you to load the generated threat catalogue into Threat Dragon for diagrammatic review and collaboration.

Do I need a Data Flow Diagram before starting threat modeling?

Yes, a Data Flow Diagram (DFD) is required before starting this threat modeling process. The DFD must be provided as a markdown file at the projects architecture path to anchor the STRIDE analysis to your project's specific trust boundaries and data flows.

When should I run a STRIDE threat model analysis for my project?

You should run a STRIDE threat model analysis during pre-launch security reviews and as an ongoing practice for your apps and services. It is also designed as an expert companion to escalate security warnings identified during launch checks.