threat-model SKILL.md skillA

threat-model from q00/ouroboros is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add q00/ouroboros/threat-model@git:20261024.1e7b434

Pins git:20261024.1e7b434 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
q00/ouroboros
Path
.claude/skills/threat-model/SKILL.md
Versions recorded
1
Latest version
git:20261024.1e7b434, committed Oct 24, 2026
Size
8,204 bytes
Repository stars
6,381
License
MIT

Build a threat model for a target codebase. Three modes: "interview" walks an application owner through the four-question framework and produces a threat model from their answers; "bootstrap" derives a threat model from the code plus past vulnerabilities (CVEs, git history, pentest reports) when no owner is available; "bootstrap-then-interview" chains the two when both owner and codebase are present. All write THREAT_MODEL.md in a shared schema. Use when asked to "threat model…

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# threat-model

A threat model answers **"what could go wrong with this system, who would do
it, and what should we do about it?"** independently of whether any specific
bug has been found yet. It is the map; vulnerability discovery is the metal
detector. A good threat model tells the pipeline where to look and tells triage
which findings matter.

**Litmus test:** If patching one line of code makes an entry disappear, it was
a vulnerability, not a threat. A threat ("attacker achieves RCE via untrusted
media parsing") still stands after every known bug is fixed; a vulnerability
("`dr_wav.h:412` doesn't bounds-check `chunk_size`") does not. This skill
produces threats. Vulnerabilities appear only as **evidence** that raises a
threat's likelihood score.

**Invocation:** `/threat-model [bootstrap-then-interview|bootstrap|interview] <target-dir> [flags]`

---

## Step 0 — Safety preamble (always runs first)

This skill performs **static analysis only**. It reads source, git history,
and any vulnerability reports the user supplies, and writes a single output
file (`docs/security/THREAT_MODEL.md`). It does not build, execute, fuzz, or
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_im5pty62s33uqio4/18ef22c45962ab82005b4e1ac5e5d76db71ac7de2e9e72782b52b50d58d7d34e.json

Then /plugin install threat-model@markdownregistry-im5pty62s33uqio4 in Claude Code. It installs git:20261024.1e7b434, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add q00/ouroboros/threat-model@sha256:18ef22c45962ab82

The line at the top of this page pins the label git:20261024.1e7b434, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_im5pty62s33uqio4.svg)](https://markdownregistry.com/a/art_im5pty62s33uqio4)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in q00/ouroboros/threat-model since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of threat-model from somewhere else? Ask it: where did my threat-model come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 1 version of this file, committed on Oct 24, 2026.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261024.1e7b434 latest2026-10-24 1e7b434 8,204 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (8204 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

q00/ouroboros · 6,381 stars · license MIT · pushed 2026-11-19 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_im5pty62s33uqio4
GET https://markdownregistry.com/api/v1/resolve?ref=q00/ouroboros/threat-model
GET https://markdownregistry.com/api/v1/blob/18ef22c45962ab82005b4e1ac5e5d76db71ac7de2e9e72782b52b50d58d7d34e

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from q00/ouroboros

triage SKILL.md skill
q00/ouroboros · .claude/skills/triage/SKILL.md · Triage a batch of raw security findings. Verify each is real,
git:20261024.1e7b434 · audit A · 6,381 stars
vuln-scan SKILL.md skill
q00/ouroboros · .claude/skills/vuln-scan/SKILL.md · Static source-code vulnerability scan. Reads a target directory (and THREAT_MODEL.md if present), spawns parallel…
git:20261024.1e7b434 · audit A · 6,381 stars
AGENTS.md AGENTS.md file
q00/ouroboros · AGENTS.md
git:20261030.cc886c1 · audit A · 6,381 stars
CLAUDE.md CLAUDE.md file
q00/ouroboros · CLAUDE.md
git:20260927.9231c1b · audit A · 6,381 stars
llms-full.txt llms.txt file
q00/ouroboros · llms-full.txt
git:20261113.f6de1ce · audit A · 6,381 stars
llms.txt llms.txt file
q00/ouroboros · llms.txt
git:20261113.f6de1ce · audit A · 6,381 stars
auto SKILL.md skill
q00/ouroboros · skills/auto/SKILL.md · Use when the work spans several files or replaces a framework, language, auth, storage, or API layer (rewrites and…
git:20261116.64a2b2e · audit A · 6,381 stars
brownfield SKILL.md skill
q00/ouroboros · skills/brownfield/SKILL.md · Scan and manage brownfield repository/worktree defaults for interviews
git:20261116.64a2b2e · audit A · 6,381 stars
cancel SKILL.md skill
q00/ouroboros · skills/cancel/SKILL.md · Cancel stuck or orphaned executions
git:20261116.64a2b2e · audit A · 6,381 stars
ouroboros-config SKILL.md skill
q00/ouroboros · skills/config/SKILL.md · Open or drive the Ouroboros settings GUI (browser, TUI, or conversational fallback)
git:20261116.64a2b2e · audit A · 6,381 stars
evaluate SKILL.md skill
q00/ouroboros · skills/evaluate/SKILL.md · Use when the user wants proof that finished work meets its acceptance criteria, not just that tests pass: 'verify it is…
git:20261116.64a2b2e · audit A · 6,381 stars
evolve SKILL.md skill
q00/ouroboros · skills/evolve/SKILL.md · Start or monitor an evolutionary development loop
git:20261116.64a2b2e · audit A · 6,381 stars

Every file in q00/ouroboros

Other files named threat-model

threat-model SKILL.md skill
me2resh/apexyard · .claude/skills/threat-model/SKILL.md · STRIDE threat modelling — spoofing, tampering, repudiation, disclosure, DoS, EoP. Deep-dive for /launch-check security.
git:20261008.3d1669c · audit A · 551 stars
threat-model SKILL.md skill
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/threat-model/SKILL.md · Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model…
git:20260606.a4decec · audit A · 550 stars
threat-model SKILL.md skill
amirfish1/claude-command-center · plugin/skills/threat-model/SKILL.md · Use before shipping a change that touches a trust boundary (a new endpoint, input parser, file-path handler, subprocess…
git:20261009.a664025 · audit B · 220 stars
threat-model SKILL.md skill
haabe/mycelium · plugins/mycelium/skills/threat-model/SKILL.md · Use to conduct STRIDE threat modeling for a system or feature design.
git:20261007.33e0656 · audit A · 54 stars
threat-model SKILL.md skill
qa-aman/claude-skills · skills/by-role/security/threat-model/SKILL.md · Write a threat model document. Use when the user says "threat model", "threat modeling", "STRIDE analysis", "attack…
git:20260303.8412b01 · audit A · 27 stars
threat-model SKILL.md skill
byerlikaya/claude-starter-kit · plugin/skills/threat-model/SKILL.md · Scope a security audit BEFORE scanning, to cut false positives: map assets, entry points, trust boundaries and 5-8…
git:20260926.aaa5dbc · audit A · 26 stars
threat-model SKILL.md skill
byerlikaya/claude-starter-kit · kit/skills/threat-model/SKILL.md · Scope a security audit BEFORE scanning, to cut false positives: map assets, entry points, trust boundaries and 5-8…
git:20260926.aaa5dbc · audit A · 26 stars
threat-model SKILL.md skill
perrylink/dsh-skill-pack-security · skills-en/threat-model/SKILL.md · Lightweight threat modeling for new features/systems: fix the target, scope and trust boundaries, asset inventory…
v2.2.25 · audit A · 23 stars

Browse by kind, by grade A, or by owner.