security-threat-model

Generate evidence-grounded threat models with Mermaid diagrams and structured tables.

Updated Jun 18, 2026
One-click install
npx skills add https://github.com/rodrigotoledo/trading-exchange --skill security-threat-model-rodrigotoledo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/rodrigotoledo/trading-exchange/tree/main/packages/skills-catalog/skills/%28security%29/security-threat-model
Command: npx skills add https://github.com/rodrigotoledo/trading-exchange --skill security-threat-model-rodrigotoledo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps security engineers generate repo-specific threat models anchored to concrete evidence in the codebase, enabling targeted risk assessment and mitigation planning.

Core Features & Use Cases

  • Anchor architectural claims to repository evidence and component interactions.
  • Enumerate trust boundaries, assets, attacker capabilities, abuse paths, and mitigations to produce a concise threat model.
  • Output a markdown threat model suitable for review and remediation planning.

Quick Start

Provide the repository path and optional in-scope paths to generate an evidence-grounded threat model for the specified scope.

Frequently Asked Questions about security-threat-model

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

FAQPage Schema
How do I generate a threat model from source code in a repository?

Generate a repo-grounded threat model by providing a repository path to enumerate trust boundaries, assets, and abuse paths anchored to architectural evidence. The tool analyzes codebase interactions to produce a structured threat model with mitigations and a Mermaid diagram.

What is repo-grounded threat modeling and how does it work?

Repo-grounded threat modeling anchors architectural claims to specific repository paths and component interactions. It enumerates trust boundaries, attacker capabilities, and abuse paths to produce an evidence-backed risk analysis narrative directly from the codebase.

Can I scope a threat model to specific paths within my codebase?

Yes, you can provide optional in-scope paths alongside the repository path to generate an evidence-grounded threat model for a specific scope. This narrows the risk analysis to targeted components and their architectural interactions.

What is the best way to document trust boundaries and attacker capabilities for AppSec?

Document trust boundaries and attacker capabilities by mapping architectural claims to repository evidence. This produces a concise markdown threat model with a structured table and a compact Mermaid diagram for review and remediation planning.

Does this threat modeling approach work without external dependencies or components?

Yes, the threat modeling skill operates without external dependencies or components. It directly analyzes your repository structure to extract architectural context and tie risk analysis claims to concrete codebase evidence.

What format is the threat model output in for remediation planning?

The threat model output is a markdown document suitable for review and remediation planning. It includes a structured threat-model table tying architectural claims to repo paths, plus a compact Mermaid diagram illustrating the architecture.