Use when the user asks for a repository-wide or scoped-path security scan.
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 Scan
Used when a user wants to audit an entire repository or a user-specified path, package, folder, or submodule-like scope for security vulnerabilities. Keep the scan phases separate and produce final HTML and markdown reports.
## Phase Sequence
Keep these phases distinct and run them in linear order:
1. `$threat-model`
2. `$finding-discovery`
3. `$validation`
4. `$attack-path-analysis`
5. Generate final output
Treat this skill as the top-level orchestrator for the four skills plus the final report assembly step. Do not collapse the phases together.
For each phase:
1. Read that phase's skill.
2. Load only the inputs required for that phase.
3. Complete that phase's workflow and checklist.
4. Only then read the next phase's skill.
Do not read ahead into later-phase skills until the current phase has completed.
Do not amortize effort across phases: complete each phase to the full depth expected by that phase before moving on.
If user requests a repo-side scan or a scoped scan, stop and ask for authorization for subagents now before setting up the goal.
## Goal Setup
…
The line at the top of this page pins the label git:20260919.7b075ca, 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 (15044 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_kll22iubd34usaeq
GET https://markdownregistry.com/api/v1/resolve?ref=cowork-os/cowork-os/security-scan
GET https://markdownregistry.com/api/v1/blob/4f8bea1a99bcb8d2e7bf7a6e0c81940194820777d64dad6de4056b2a4f96438b
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/threat-model/SKILL.md · Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model…
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…
fusengine/agents · plugins/security-expert/skills/security-scan/SKILL.md · Use when scanning for XSS, SQL injection, command injection, hardcoded secrets, or any OWASP Top 10 vulnerability…
ray0907/security-scan · SKILL.md · Use when a user asks to scan a repository for dependency vulnerabilities, license compliance, insecure code patterns…
