tm-status

Analyze local threat model JSON and YAML files to output a structured security status summary.

8|1|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/josemlopez/threat-modeling-toolkit --skill tm-status
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tm-status
Source: https://github.com/josemlopez/threat-modeling-toolkit/tree/main/skills/tm-status
Command: npx skills add https://github.com/josemlopez/threat-modeling-toolkit --skill tm-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a concise, at-a-glance view of the current threat model, including asset counts, threat distribution, control verification, and compliance coverage, helping security teams rapidly assess posture.

Core Features & Use Cases

  • Overview dashboards: Summarize assets, threats, controls, and gaps in a single view.
  • Compliance visibility: Show coverage for frameworks (e.g., OWASP, SOC2) across the model.
  • Use Case: A security engineer runs /tm-status to quickly verify that assets and controls align with baseline before a release.

Quick Start

Run the status check to display the current threat model overview.

Frequently Asked Questions about tm-status

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

FAQPage Schema
How do I get a quick status overview of my threat model?

To get a threat model status overview, run a status check that loads local JSON artifacts and YAML configuration to summarize assets, threats, controls, gaps, and compliance posture for security reviews.

What is included in a threat model compliance and risk posture summary?

A threat model compliance and risk summary includes asset counts, threat distribution, control verification, and framework coverage like OWASP or SOC2 to help security teams rapidly assess posture.

How do I verify threat model controls and assets align before a release?

Verify threat model controls and assets before a release by generating a structured posture summary that checks control verification and compliance gaps against your baseline requirements.

Do I need external security tools to check my threat model status?

You do not need external security tools to check threat model status because the process reads local threat model JSON artifacts and YAML configuration directly without external dependencies.

Can I use threat model status summaries for SOC2 and OWASP compliance visibility?

You can use threat model status summaries for SOC2 and OWASP compliance visibility because the output displays framework coverage across the model to identify gaps in your security posture.

What are the limitations of using local artifacts for threat model posture reviews?

The limitation of using local artifacts for threat model posture reviews is that the status overview is restricted to reading local JSON artifacts and YAML configuration, requiring no external tools.