security-threat-model

Generates repository-grounded threat models with trust boundaries, abuse paths, and prioritized mitigations.

1|Updated Jul 16, 2026
One-click install
npx skills add https://github.com/sota411/codex-config --skill security-threat-model-sota411
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: security-threat-model
Source: https://github.com/sota411/codex-config/tree/main/user-skills/security-threat-model
Command: npx skills add https://github.com/sota411/codex-config --skill security-threat-model-sota411

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Security reviews often produce generic checklists disconnected from the actual codebase. This Skill produces an AppSec-grade threat model anchored to real repository evidence, with explicit assumptions, prioritized abuse paths, and concrete mitigations. ## Core Features & Use Cases - Evidence-Anchored Modeling: Maps components, data flows, trust boundaries, and entry points directly to repo paths and symbols, never inventing architecture. - Prioritized Threat Enumeration: Generates attacker-goal-driven abuse paths with qualitative likelihood, impact, and priority ratings calibrated to the repo's real exposure. - Interactive Assumption Validation: Pauses to confirm deployment model, auth expectations, and data sensitivity with the user before finalizing the report. - Use Case: Point it at a web service repository to receive a Markdown threat model with a Mermaid diagram, threat table (TM-001...), and a list of focus paths for deeper manual security review. ## Quick Start Ask the AI to create a repository-grounded threat model for this codebase with prioritized abuse paths and mitigations.

Frequently Asked Questions about security-threat-model

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

FAQPage Schema
How do I create a threat model for a code repository?▼

Provide the repo root path and any known context like deployment model and internet exposure. The skill maps components, trust boundaries, and entry points from actual code evidence, then enumerates prioritized abuse paths and mitigations in a structured Markdown report.

What does a repo-grounded threat model include?▼

It includes a system model with a Mermaid diagram, an asset table, attacker capabilities and non-capabilities, 5-10 abuse paths, a threat table with likelihood and priority ratings, and focus paths for deeper manual security review.

Does this threat modeling skill work for CLI tools and libraries?▼

Yes, it adapts to servers, CLIs, libraries, and workers by identifying how the system runs and its entrypoints. It separates runtime behavior from CI/build tooling and tests to keep the analysis scoped correctly.

When should I not use this threat modeling skill?▼

It is not suited for general architecture reviews or generic code review tasks. It activates only on explicit threat modeling requests and requires enough repository access to ground claims in evidence.

Why does the threat model ask questions before finishing?▼

The workflow pauses to validate assumptions about deployment model, auth expectations, data sensitivity, and exposure that materially affect risk ranking. If you cannot answer, it proceeds with explicit assumptions and marks conditional conclusions.