threat-model
Skill2 starsChanged 17 days agoMITView on GitHub
Build a threat model for a repository, service, or feature before it ships. Use when asked to threat model, review security design, assess attack surface, or answer "what could go wrong" about a system.
57 other projects use a version of this.
Adopted by
Most recently taken up by
- requie/endostacktheir own version, first seen Nov 8, 2026
- pat-lewczuk/skillstheir own version, first seen Nov 1, 2026
- Codeminer42/skillstheir own version, first seen Nov 1, 2026
- jmanico/grim-promptertheir own version, first seen Nov 1, 2026
- Q00/ouroborostheir own version, first seen Oct 25, 2026
- kenhuangus/defense-factory-skillstheir own version, first seen Oct 25, 2026
Used with
Projects with it also use vuln-scan, supply-chain-review and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AnthropicSkillvuln-scan
Static source-code vulnerability scan. Reads a target directory (and THREAT_MODEL.md if present), spawns parallel review subagents per focus area, and writes VULN-FINDINGS.json + .md for /triage to consume. Read-only — no building, running, or network. For execution-verified crashes, use vuln-pipeline instead. Use when asked to "scan for vulns", "review this code for security issues", "find bugs in <dir>", or as the step between /threat-model and /triage.
Also in 5 projects that use this
MesteriisSkillsupply-chain-review
Reviews lockfiles, installers, provenance, CI permissions, dependency confusion, artifacts, registries, and publishing.
Also in 3 projects that use this
AnthropicSkillpatch
Generate candidate fixes for verified security findings. Consumes
Also in 4 projects that use this
mbwsimsSkillorbit
Run for repo-wide or diff-wide readiness sweeps: "/orbit", "/orbit pr", "/orbit deep", "/orbit quick", "audit this project", "project-wide review", "is this PR ready overall", or "combined security, tests, codebase, evolution, and instruction review". Use this for broad multi-system assessment, not for a single-file review or a one-domain question.
Also in 3 projects that use this
mbwsimsSkilltest-plan
This skill should be used when the user asks to "plan tests", "what should I test", "what tests do I need", "test plan for", "testing strategy for", "test matrix for", "what cases should I cover", "help me plan tests", mentions "/test-plan", or wants to understand what tests are needed before writing any test code.
Also in 3 projects that use this
Sagargupta16Skilldependency-audit
Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.
Also in 4 projects that use this
Other versions57 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 57
- openai/codex-security★ 14ksame name
- openai/plugins★ 7.8ksame name
- anthropics/defending-code-reference-harness★ 7.5ksame name
- Q00/ouroboros★ 6.4ksame name
- me2resh/apexyard★ 542same name
- jmanico/grim-prompter★ 497same name
- Cosmian/kms★ 372same name
- mbwsims/claude-universe★ 71same name
- navikt/copilot★ 61same name
- Codeminer42/skills★ 32same name
47 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- cve-researchSkill
- harden-serviceSkill
- review-diff-for-vulnsSkill
- triage-alertSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 51 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Before a release that changes authentication, authorization, or data storage.
- Distinctive: line 52
Never downgrade a reachable high-severity finding to make a report look clean.
“Common” is measured: kept by at least 6 in 10 of the 51 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Threat model
Produce a threat model grounded in the code that actually exists. Never invent components the repository does not contain.
When to use
- A new service, endpoint, or data flow is being designed or reviewed.
- Someone asks "is this secure", "what could an attacker do", or "what are the risks".
- Before a release that changes authentication, authorization, or data storage.
Procedure
- Establish scope. Name the components under review and read their entry points (routes, handlers, queue consumers, CLI commands). Note what is explicitly out of scope. Done when: every entry point has a file path and a line number.
- Map the data flow. For each entry point record: untrusted input, trust boundary crossed, data store touched, and outbound calls made. Trust boundaries are where validation must exist. Done when: each flow names the validation function that actually guards the boundary, or is marked unguarded.
- Enumerate threats with STRIDE against each flow. Skip categories that cannot apply, and say why. Done when: every flow has threats or an explicit "not applicable" note.
- Rank by reachability. For each threat state the concrete attacker action, the preconditions, and whether the code path is reachable today. Unreachable findings go in a separate section. Done when: each threat is labelled reachable, conditional, or unreachable, with evidence.
- Recommend controls that are proportionate and implementable in the existing design. Each recommendation names the file it would touch. Done when: every reachable threat has at least one control or an accepted-risk note.
Output format
## Scope
## Data flows
| flow | entry point | trust boundary | validation | store | outbound |
## Threats
| id | flow | STRIDE | attacker action | preconditions | reachability | evidence |
## Recommendations
| threat | control | file | effort |
## Accepted risksRules
- Cite file and line for every claim. No citation, no finding.
- Say "no issues found by ruleset vX" rather than "safe".
- Never downgrade a reachable high-severity finding to make a report look clean.
- Secrets found during review are reported by fingerprint only, never by value.
Anti-patterns
- Threat modelling a diagram instead of the code.
- Copying a generic OWASP checklist without mapping it to real entry points.
- Reporting volume instead of reachability.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

