deep-audit SKILL.md skillA
deep-audit from pedrohcgs/claude-code-my-workflow is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add pedrohcgs/claude-code-my-workflow/deep-audit@git:20260927.7650048Pins git:20260927.7650048 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- pedrohcgs/claude-code-my-workflow
- Path
.claude/skills/deep-audit/SKILL.md- Versions recorded
- 7
- Latest version
- git:20260927.7650048, committed Sep 27, 2026
- First version recorded
- Jun 9, 2026
- Size
- 11,604 bytes
- Repository stars
- 1,718
- License
- MIT
Comprehensive adversarial audit of a theory, proof, math/econ paper, codebase, or set of claims — decompose into components, fan out independent skeptics that must return CONCRETE defects, adjudicate every finding with a separate judge, fix all confirmed defects, then re-verify. Use when correctness must be bulletproof and single-pass or round-by-round review is too slow and too shallow. Invoke for "audit this rigorously", "find ALL the bugs/gaps", "make this rock solid…
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
# Deep adversarial audit A convergent alternative to slow round-by-round review. Instead of one reviewer finding one or two issues per pass, fan out many independent skeptics over the *whole* artifact at once, adjudicate what they find, fix everything confirmed, and re-verify. Modeled on the multi-agent methodology behind hard formal-proof efforts (diverse independent portfolio, adversarial throughout, concrete evidence only, synthesize-challenge-repeat). ## When to reach for this - The artifact is dense enough that a single review keeps surfacing *new* issues each pass (the tell that round-by-round is the wrong tool). - Correctness is the priority and the cost of a missed defect is high (a paper going to a top venue, a proof, a security-sensitive change, a migration). - The user asked to "fix ALL of it", "be deeper", "converge faster", "100% rock solid". Requires the user to have opted into multi-agent orchestration (they asked for a workflow / deep audit / to fan out agents, or ultracode is on). If they haven't, propose it and its rough cost first. ## The method …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_we33xonxjcjscut2/d1cbf2061f98612e27e1aaffa2bbe8f88f5e00c9967b3dcdbfa5c77d59118106.json
Then /plugin install deep-audit@markdownregistry-we33xonxjcjscut2 in Claude Code. It installs git:20260927.7650048, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add pedrohcgs/claude-code-my-workflow/deep-audit@sha256:d1cbf2061f98612eThe line at the top of this page pins the label git:20260927.7650048, 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.
[](https://markdownregistry.com/a/art_we33xonxjcjscut2)
3 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in pedrohcgs/claude-code-my-workflow/deep-audit 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 deep-audit from somewhere else? Ask it: where did my deep-audit 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 7 versions of this file, between Jun 9, 2026 and Sep 27, 2026, about one every 18 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260927.7650048 latest | 2026-09-27 | 7650048 | 11,604 B | A | view · diff |
| git:20260927.0425fd6 | 2026-09-27 | 0425fd6 | 11,573 B | A | view · diff |
| git:20260927.6535de7 | 2026-09-27 | 6535de7 | 11,178 B | A | view · diff |
| git:20260821.6600333 | 2026-08-21 | 6600333 | 11,052 B | A | view · diff |
| v1.0.0 | 2026-08-21 | 6fe4b52 | 12,482 B | A | view · diff |
| v1.0.0 | 2026-08-21 | 8a2f894 | 10,780 B | A | view · diff |
| v1.0.0 | 2026-06-09 | 1ebee45 | 10,745 B | A | view |
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.
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.
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.
Installed this file, say at .claude/skills/deep-audit/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (11604 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
pedrohcgs/claude-code-my-workflow · 1,718 stars · license MIT · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_we33xonxjcjscut2 GET https://markdownregistry.com/api/v1/resolve?ref=pedrohcgs/claude-code-my-workflow/deep-audit GET https://markdownregistry.com/api/v1/blob/d1cbf2061f98612e27e1aaffa2bbe8f88f5e00c9967b3dcdbfa5c77d59118106
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.