security-threat-model

Identify repository components, data flows, trust boundaries, and assets for threat modeling.

Updated Feb 4, 2026
One-click install
npx skills add https://github.com/pchemguy/Dummy --skill security-threat-model-pchemguy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/pchemguy/Dummy/tree/main/docs/AgentSkills/openai/skills/skills/.curated/security-threat-model
Command: npx skills add https://github.com/pchemguy/Dummy --skill security-threat-model-pchemguy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Repository-grounded threat modeling that anchors every architectural claim to repo evidence and explicit assumptions, delivering an actionable AppSec-grade threat model.

Core Features & Use Cases

  • Repo-specific threat modeling anchored to evidence in the repository.
  • Explicit assumptions and evidence anchors for all claims, with prioritization of attacker goals.
  • Output includes mitigations, detection ideas, and a compact diagram for quick review.

Quick Start

Follow the workflow described in the SKILL to identify scope, assets, boundaries, and threats for the target repository.

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 for a specific application repository?

To generate a threat model for a specific application repository, use this Skill to identify repo components, data flows, and trust boundaries. It anchors every architectural claim to repository evidence and outputs prioritized abuse-path threats with mitigations.

What is evidence-grounded threat modeling in AppSec?

Evidence-grounded threat modeling in AppSec anchors every architectural claim to evidence in the repository paths and prompts. It explicitly states assumptions when evidence is missing to deliver a repository-specific threat model.

How do I identify trust boundaries and assets for risk analysis?

Identify trust boundaries and assets for risk analysis by following the Skill workflow to map repository components and data flows. It grounds these architectural elements in repo evidence to prioritize attacker goals and abuse paths.

Does this threat modeling approach work without external dependencies?

Yes, this threat modeling approach works without external dependencies. It operates standalone to analyze repository components and data flows directly from the codebase to produce an AppSec-grade threat model.

Can I generate a Mermaid diagram for my application threat model?

Yes, you can generate a compact Mermaid diagram for your application threat model. The Skill output includes a diagram for quick review along with prioritized abuse-path threats and detection ideas.

What is the best way to document AppSec mitigations for identified threats?

The best way to document AppSec mitigations is to ground them in repository evidence using this Skill. It produces a prioritized set of abuse-path threats paired with concrete mitigations and detection ideas suitable for AppSec review.