Security Threat Model (Repository-grounded)

What it does

This skill packages an upstream threat-model workflow so an operator can produce an AppSec-grade, repository-grounded threat model. It drives a focused analysis: scoping components and entrypoints, enumerating trust boundaries and assets, mapping realistic attacker capabilities, enumerating abuse paths, and producing prioritized mitigations tied to concrete files or locations in the repo. The output is a concise Markdown threat-model file that preserves provenance and references to the copied upstream artifacts.

When to use it

Use this skill when you need a threat model that is specific to a codebase or path — for example, before a security review, PR, or release. Do NOT use it for general architecture summaries or generic security checklists. Use it when provenance matters and when the operator should preserve upstream workflow, support files, and evidence.

What's included

• Scripts: none bundled (has_scripts=false)
• References: preserved copied reference files (has_references=true), e.g. prompt-template.md and security-controls-and-assets.md
• Instructions: step-by-step scoping, boundary enumeration, threat enumeration, likelihood/impact prioritization, and mitigation recommendations. The skill also prescribes a quality-check and a final markdown filename format.

Compatible agents

Inferred compatibility: codex-cli, claude-code, cursor, gemini-cli and other developer-oriented agent harnesses that can read repository files and run scripted prompts.