Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/vcnoc/claude-code-zen-mcp-skill-work/codex-code-reviewernpx skills add VCnoC/Claude-Code-Zen-mcp-Skill-Work --skill codex-code-reviewergit clone --depth 1 https://github.com/VCnoC/Claude-Code-Zen-mcp-Skill-WorkWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/vcnoc/claude-code-zen-mcp-skill-work/codex-code-reviewer)<a href="https://agentmods.dev/skills/vcnoc/claude-code-zen-mcp-skill-work/codex-code-reviewer"><img src="https://agentmods.dev/badge/skills/vcnoc/claude-code-zen-mcp-skill-work/codex-code-reviewer.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00096 | $0.03475 |
| Opus 5 | $0.00048 | $0.01737 |
| Sonnet 5 | $0.00019 | $0.00695 |
| Haiku 4.5 | $0.00010 | $0.00347 |
Grade A, and why
codex-code-reviewer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Code Reviewer
Overview
This skill provides a systematic, iterative code review workflow powered by zen mcp's codex tool. It automatically checks recently modified code files against project standards (CLAUDE.md requirements), presents identified issues to users for approval, applies fixes, and re-validates until code quality standards are met or the maximum iteration limit is reached.
Operation Modes:
- Interactive Mode (Default): Present issues to user, wait for approval before applying fixes
- Full Automation Mode: Automatically select and apply all suggested fixes without user approval (activated when user initially requests "full automation" or "complete automation")
When to Use This Skill
Trigger this skill when the user says:
- "Use codex to check the code"
- "Please help me check if the recently generated code has any issues"
- "Check the code after each generation"
- Similar requests for code quality validation using codex
Workflow: Iterative Code Review Cycle
Prerequisites
Before starting the review cycle:
- ** Read Operation Mode from Context (automation_mode - READ FROM SSOT):**
- automation_mode definition and constraints: See CLAUDE.md「📚 共享概念速查」
- This skill's role: Skill Layer (read-only), read from context
[AUTOMATION_MODE: true/false], true → auto-fix / false → ask user
1a. Read Coverage Target from Context (coverage_target - READ FROM SSOT):
- coverage_target definition and constraints: See CLAUDE.md「📚 共享概念速查」
- This skill's role: Skill Layer (read-only), read from context
[COVERAGE_TARGET: X%], validate coverage (≥ target pass, < 70% reject)
-
Identify Files to Review:
- Use
git statusor similar to identify recently modified files - Interactive Mode (automation_mode = false): Confirm with user which files should be reviewed
- Automated Mode (automation_mode = true): Auto-select all recently modified files, log decision to auto_log.md
- Use
-
Initialize iteration counter:
current_iteration = 1 -
Set maximum iterations:
max_iterations = 5 -
Initialize review tool tracker:
first_review_done = false -
Detect Review Context:
- Check if this is final quality validation (project completion/final verification)
- If YES: Enable Final Validation Mode (requires minimum 2 passes: codereview + clink)
- If NO: Use Standard Review Mode
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/code_quality_standards.md 1.8 KB
- references/quality_standards/commit_and_quality_gates.md 633 B
- references/quality_standards/core_principles.md 1.4 KB
- references/quality_standards/error_handling_and_usage.md 1.4 KB
- references/quality_standards/global_rules.md 1.9 KB
- references/quality_standards/p3_constraints_and_quality.md 2.1 KB
- references/quality_standards/README.md 1.2 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 5d ago First seen · 341 lines · 96 tokens per session scan A da895ae87515
codex-code-reviewer is a skill published in the GitHub repository VCnoC/Claude-Code-Zen-mcp-Skill-Work (116 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 96 tokens to every session and 3,475 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…