security-threat-model
Repository-grounded threat modeling that enumerates trust boundaries, assets, attacker capabilities, abuse paths, and mitigations, and writes a concise Markdown threat model. Trigger only when the user explicitly asks to threat model a codebase or path, enumerate threats/abuse paths, or perform AppSec threat modeling. Do not trigger for general architecture summaries, code review, or non-security design work.
Security Assessment
About security-threat-model
The 'security-threat-model' skill provides automated, repository-grounded threat modeling to identify and analyze potential security risks within a codebase or specific project paths. It solves the problem of ad-hoc or generic threat modeling by delivering actionable, evidence-backed AppSec assessments. By focusing on concrete trust boundaries, assets, entry points, and realistic attacker capabilities, this skill ensures that security evaluations are grounded in the actual architecture and components of the repository, rather than hypothetical or checklist-based approaches.
Key features include the ability to extract and scope system components from the repository, identify assets and trust boundaries, enumerate realistic attacker capabilities, and produce a prioritized list of threats as abuse paths. It supports explicit likelihood and impact reasoning, validation of assumptions with the user, and generation of concrete mitigation recommendations tied to specific components, boundaries, or controls. The workflow emphasizes evidence-based claims and user confirmation of critical assumptions, ensuring that the threat model is both accurate and actionable.
This skill is particularly useful for security engineers, developers responsible for application security, and DevSecOps teams who need to perform threat modeling directly against a repository. It is ideal when assessing new features, deployment scenarios, or internet-exposed components, and for organizations aiming to integrate security analysis into their development lifecycle. Users benefit from precise, high-quality threat assessments that can guide mitigation planning and strengthen overall application security posture.
FAQ
When should I use this skill?
Use this skill when you need to threat model a codebase or a specific project path, enumerate threats or abuse paths, or perform application security-focused threat analysis. It should not be used for general architecture summaries or code reviews.
What inputs does the skill require?
The skill requires the repository root path and any in-scope paths, intended usage, deployment model, internet exposure, authentication expectations, and optionally any existing repository summary or architecture specification.
Can this skill work on any programming language or framework?
The skill is repository-agnostic and focuses on components, data flows, and entry points within the codebase. It does not rely on a specific programming language but requires access to the repository structure and components.
Are there limitations or assumptions I should be aware of?
The skill assumes that architectural claims and component identification can be grounded in the repository. Non-evidence-based assumptions are avoided, and users are prompted to confirm critical context such as deployment model, scale, and exposure. If context is missing, assumptions will be explicitly stated.
What kind of output does the skill produce?
It produces a concise Markdown threat model anchored to repository evidence, including enumerated threats, impacted assets, likelihood and impact ratings, prioritized risk ranking, and recommended mitigations tied to specific components or controls.
Install security-threat-model
Quick Setup:
- Copy the skill folder to
.claude/skills/ - Claude will automatically detect and use the skill
Repository
openai/skills