tmdd-threat-modeling

Generate code-grounded YAML threat models with lint-validated outputs.

33|2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/attasec/tmdd --skill tmdd-threat-modeling
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tmdd-threat-modeling
Source: https://github.com/attasec/tmdd/tree/main/.cursor/skills/threat-model
Command: npx skills add https://github.com/attasec/tmdd --skill tmdd-threat-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Threat modeling often relies on generic templates. This skill grounds threat modeling in the actual codebase architecture, producing actionable YAML threat models that reflect real components, data flows, and technologies to guide secure development decisions.

Core Features & Use Cases

  • Architecture-driven threat modeling grounded in real code paths (components, data flows, and technologies).
  • Automated generation of threats and mitigations tied to specific files/endpoints, with support for incremental updates in existing threat models.
  • Integration with tmdd commands for linting, initialization, and feature planning, enabling reproducible security reviews across deployments.
  • Facilitates collaboration between developers and security analysts by generating machine-readable YAML artifacts under .tmdd/.

Quick Start

Invoke the tmdd threat-modeling workflow to analyze your repository and generate a code-grounded threat model.

Frequently Asked Questions about tmdd-threat-modeling

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

FAQPage Schema
How do I generate a threat model from my codebase architecture?

Yes, you can incrementally update existing threat models by applying the tmdd workflow during feature planning. It traces new data flows and components against the current architecture, appending validated threats and mitigations to the existing YAML artifacts.

What is the best way to ground threat modeling in real code paths instead of generic templates?

Threat modeling with tmdd outputs machine-readable YAML artifacts stored under the .tmdd directory. These files contain mapped components, traced data flows, and generated threats with mitigations, using strict ID conventions and lint-validated outputs for reproducible security reviews.

Do I need YAML linting to validate threat model artifacts?

Yes, YAML linting validates threat model artifacts to ensure strict ID conventions and reproducible security reviews. The tmdd commands integrate initialization, feature planning, and linting to enforce consistent, machine-readable outputs under the .tmdd directory.

Can I use tmdd for threat modeling across multiple deployments and security reviews?

Yes, you can use tmdd for reproducible security reviews across deployments. It integrates initialization, feature planning, and linting commands to generate consistent YAML threat models grounded in your codebase architecture, facilitating collaboration between developers and security analysts.