codex-review SKILL.md skillA
codex-review from arjunrajlaboratory/mycelium is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add arjunrajlaboratory/mycelium/codex-review@git:20261013.2329b1fPins git:20261013.2329b1f in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- arjunrajlaboratory/mycelium
- Path
skills/codex-review/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261013.2329b1f, committed Oct 13, 2026
- First version recorded
- Aug 3, 2026
- Size
- 10,382 bytes
- Repository stars
- 72
- License
- MIT
Address Codex review comments on a pull request. Use when the user asks to respond to Codex, fix what Codex flagged, handle an @codex comment, or supplies a Codex review link. Generalize each comment into an error pattern, audit the whole branch for other instances, fix and test them, then draft a reply. Confirm before posting or re-triggering review. Do not use for a general code or scientific review without Codex feedback.
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
# Mycelium — Codex Review Resolve bundled `skills/` paths relative to the Mycelium plugin root (two directories above this `SKILL.md`). Resolve repository and `.living/` paths relative to the user's working repository. Handle Codex review comments on a pull request so that each review round actually converges instead of looping. The point is in Step 3: when Codex flags one instance of a mistake, the same mistake is usually elsewhere on the branch too. Fixing only the flagged line invites Codex to surface the next instance on its next pass, and you burn cycles fixing them one at a time. This skill fixes the flagged instance **and** audits the whole branch for the same error pattern. ## Why this skill exists Codex reviews a diff and flags concrete instances. It does not (and cannot reliably) tell you "and here are the four other places you made the same mistake." An LLM coding agent responding to that comment tends to fix exactly the line cited and move on — which is locally correct but globally incomplete. The result is a back-and-forth: round 1 flags `foo.py:40`, you fix it, round 2 flags `bar.py:88` (same bug), and so on. Generalizing each comment into an error …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_ip4wlhfmghzuhidf/cdba9a9255a02abe169597e0c9a8ad136a471bab551702ce568c8d759310ede0.json
Then /plugin install codex-review@markdownregistry-ip4wlhfmghzuhidf in Claude Code. It installs git:20261013.2329b1f, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add arjunrajlaboratory/mycelium/codex-review@sha256:cdba9a9255a02abeThe line at the top of this page pins the label git:20261013.2329b1f, 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_ip4wlhfmghzuhidf)
2 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 arjunrajlaboratory/mycelium/codex-review 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 codex-review from somewhere else? Ask it: where did my codex-review 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 2 versions of this file, between Aug 3, 2026 and Oct 13, 2026, about one every 72 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261013.2329b1f latest | 2026-10-13 | 2329b1f | 10,382 B | A | view · diff |
| git:20260803.57db0c3 | 2026-08-03 | 57db0c3 | 10,091 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/codex-review/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 (10382 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
arjunrajlaboratory/mycelium · 72 stars · license MIT · pushed 2026-11-16 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ip4wlhfmghzuhidf GET https://markdownregistry.com/api/v1/resolve?ref=arjunrajlaboratory/mycelium/codex-review GET https://markdownregistry.com/api/v1/blob/cdba9a9255a02abe169597e0c9a8ad136a471bab551702ce568c8d759310ede0
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 arjunrajlaboratory/mycelium
Every file in arjunrajlaboratory/mycelium