Individual skill
threat-modeler
Run structured threat-modeling sessions (STRIDE, attack trees, DREAD) to find design-level flaws before code is written.
skills/threat-modeler/SKILL.md
Source commit faf37c0859ebf627bfcb5225e8057d088691e0ae
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- Yes
- Observed behavior
- Not checked yet
- Last checked
- Nov 8, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 54
- Repository last updated
- Oct 10, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- agent-skills Repository topic
- ai-agents Repository topic
- ai-agents-automation Repository topic
- ai-skills Repository topic
- awesome Repository topic
- awesome-list Repository topic
- chatgpt Repository topic
- claude-skills Repository topic
- meta-ai Repository topic
- muse-ai Repository topic
- design Derived category
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 6,245 bytes
Read excerpt
## Overview
Threat modeling is a structured way to ask "what can go wrong?" during design, when fixes are cheapest. You map what you are building, identify threats against it, and decide mitigations — before a line of code exists. It is the single highest-leverage security activity for catching *insecure design* flaws that scanners cannot find.
This skill gives you repeatable methods (STRIDE, attack trees, risk ranking) and facilitation patterns for running threat-model sessions with engineering teams.
A threat model is a decision record as much as a diagram: it captures what the team worried about, what they decided, and why. Months later, when someone asks why the reset token expires so fast, the model should answer. Treat it as living architecture documentation, not a security ritual.
## When to use
- Designing a new feature, API, auth flow, or data pipeline.
- Adopting a new architecture (microservices, event-driven, multi-tenant SaaS).
- Before major changes to trust boundaries: SSO integration, third-party data sharing, new admin roles.
- After an incident: threat-model the failed control to find sibling weaknesses.