Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.
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
# Security Threat Model
## Objective
Establish the repository-scoped threat model at the path defined in `../../references/scan-artifacts.md`. If this already exists, stop here. If a threat model or clearly authoritative security scan guidance is provided or already exists, persist it unchanged to this file, then stop here.
`AGENTS.md` can be that authoritative source when it is sufficiently specific about the repository's product surfaces, trust boundaries, attacker-controlled inputs, assumptions, or security scan guidance to serve as the threat model.
If no threat model is provided, generate a repository-scoped threat model to be used in future bug discovery. The threat model should holistically cover the entire repository and should make it obvious:
- what assets or privileges matter
- what trust boundaries exist
- what inputs are attacker-controlled
- what invariants the code must preserve
- what repository-wide failure modes would matter most
## Artifact Resolution
The path references in this skill are the default locations for this phase.
…
The line at the top of this page pins the label git:20260606.a4decec, 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.
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 (4132 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
cowork-os/cowork-os · 535 stars · license MIT · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tjopxfvk7imrjbbh
GET https://markdownregistry.com/api/v1/resolve?ref=cowork-os/cowork-os/threat-model
GET https://markdownregistry.com/api/v1/blob/9a73305a379a6e777a2c1476174c429fdc3450c89fc1c00a66fa7eac997004fc
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.
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/attack-path-analysis/SKILL.md · Use when Codex is already in the attack-path-analysis phase of a security scan or the user explicitly asks to trace a…
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/deep-security-scan/SKILL.md · Use when the user asks for a deep, exhaustive, multi-pass, or variance-reducing repository-wide Codex Security scan…
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/finding-discovery/SKILL.md · Use when Codex is already in the finding-discovery phase of a security scan or the user explicitly asks to discover…
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/fix-finding/SKILL.md · Use when the user explicitly asks to fix and verify a validated or plausible security finding. Do not use as the…
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/security-diff-scan/SKILL.md · Use when the user asks for a security review of a pull request, commit, branch diff, working-tree patch, or other…
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/security-scan/SKILL.md · Use when the user asks for a repository-wide or scoped-path security scan.
cowork-os/cowork-os · resources/plugin-packs/codex-security/skills/validation/SKILL.md · Use when Codex is already in the validation phase of a security scan or the user explicitly asks to determine whether…
cowork-os/cowork-os · resources/skills/1password/SKILL.md · Set up and use 1Password CLI (op). Use when installing the CLI, enabling desktop app integration, signing in (single or…
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…
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…
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…
air-gapped/skills · .claude/skills/threat-model/SKILL.md · [1/4 defending-code] Build a threat model for a target codebase. Optional first step of the find-and-fix loop…
