Menu

Individual skill

threat-modeler

0upvotes

Performs proactive, pre-implementation threat modeling (STRIDE-style) for a feature or system before it's built. Use when designing something new that touches user data, auth, money, or external input, before writing code.

skills/security/threat-modeler/SKILL.md

Read pinned source

Source commit d0a9928d24afb7df0fad2f2f35f65d3938a6926a

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 5, 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)
27
Repository last updated
Aug 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

## Purpose

Identify likely threats and attack surfaces for a feature or system *before* it's built, so mitigations are designed in from the start rather than patched on after a [Security Auditor](../../development/security-auditor/) review finds them in finished code.

## When to Use

- Designing a new feature that touches user data, authentication, payments, or external/untrusted input.
- Before finalizing an architecture that introduces a new trust boundary (a new service, a new external integration, a new user-facing input).
- The user asks for a "threat model" or "what could go wrong from a security angle" on something not yet built.

Differs from [Security Auditor](../../development/security-auditor/): that skill reviews *existing* code for concrete vulnerabilities; this skill reasons about a *design* before code exists, to catch classes of risk while they're still cheap to address.

## What to Analyze / Do
Back to top