security-threat-model

Generates repository-specific threat models with Mermaid diagrams and structured tables.

1|Updated Mar 25, 2026
One-click install
npx skills add https://github.com/wangzhongyuan11/open-claude-code --skill security-threat-model-wangzhongyuan11
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/wangzhongyuan11/open-claude-code/tree/main/.opencode/skills/security-threat-model
Command: npx skills add https://github.com/wangzhongyuan11/open-claude-code --skill security-threat-model-wangzhongyuan11

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a disciplined method to produce repo-specific threat models, grounded in evidence, to guide secure software reviews and risk prioritization.

Core Features & Use Cases

  • Repo-specific threat modeling anchored to concrete repository evidence.
  • Data-flow and trust-boundary mapping with prioritized abuse-paths and mitigations.
  • Generates structured outputs (Mermaid diagrams and tables) for integration into security reviews and reports.

Quick Start

Run the threat-model tool on your repository to generate a focused AppSec threat model and mitigation plan.

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 my codebase?▼

To generate a threat model from your codebase, you run the tool on your repository to analyze components, data flows, and trust boundaries. It outputs a repo-grounded AppSec threat model, a Mermaid diagram, and a structured mitigation table.

What is repo-grounded threat modeling for AppSec reviews?▼

Repo-grounded threat modeling is a disciplined method that anchors every architectural claim to concrete evidence within your repository. It identifies runtime and CI boundaries to produce risk-prioritized abuse-paths and mitigations for secure software reviews.

Can I use this for codebases with complex CI and runtime trust boundaries?▼

Yes, this threat modeling approach is designed for codebases with clear runtime and CI boundaries. It maps data flows across these trust boundaries to prioritize abuse-paths and highlight existing security mitigations and gaps.

How do I document attack surfaces and data flows for a software project?▼

You document attack surfaces and data flows by running this tool to map repository components and trust boundaries. It generates a visual Mermaid diagram and a structured threat-model table highlighting prioritized risks and mitigation gaps.

What's the best way to prioritize risk mitigation during an application security review?▼

The best way to prioritize risk mitigation is to use a repo-grounded threat model that ranks abuse-paths across trust boundaries. It highlights existing mitigations and identifies gaps, guiding your AppSec review and mitigation planning effectively.

Does this threat modeling approach require external dependencies?▼

No, this threat modeling approach requires no external dependencies. You simply run the tool directly on your repository to generate structured outputs and mitigation plans based on the existing codebase evidence.