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 instructions/boyand/codex-review/agents-mdgit clone --depth 1 https://github.com/boyand/codex-reviewWhat 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.01034 | $0.01034 |
| Opus 5 | $0.00517 | $0.00517 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade B, and why
codex-review AGENTS.md scanned grade B with 1 finding 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 3d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- The wrapper rebuilds the Go engine to `.bin/codex-review-go`, walks a small parent-process chain to find the current Claude session file under `~/.claude/sessions/`, injects hidden `--session-pid` and `--session-id` ru How it starts
The opening of the file, as written. The whole thing — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Review — Required Behavior and Architecture
This plugin is command-driven and session-scoped.
Required product behavior
These are the non-negotiable behaviors the plugin must preserve:
- Commands must resolve the correct workflow automatically from the current Claude Code session.
- The normal user path must not require
--workflow <id>. - Multi-round
planandimplmust work with explicit user choices to move forward, repeat, or finish. - Running
/codex-review:implfromplan/approvalcounts as an explicit user choice to move forward and should auto-advance toimplement. - The canonical plan under review is
.claude/codex-review/workflows/<id>/artifacts/plan.md. - Implementation review must compare against that canonical approved plan, not a mutable native Claude plan file.
- Findings/outcomes must remain inspectable through
summaryand the workflow artifacts. - The normal flow is command-driven. Hidden hook progression is not part of the default architecture.
High-level architecture
Workflows live under:
.claude/codex-review/workflows/<workflow-id>/
Key files:
workflow.json— workflow state for phase, round, owner session, status, and plan sourcedecisions.tsv— normalized findings/outcome ledger used bysummaryartifacts/plan.md— sticky canonical plan snapshotartifacts/plan-review-rN.mdandartifacts/plan-findings-rN.mdartifacts/implement-review-rN.mdandartifacts/implement-findings-rN.md
Runtime model:
- The tracked wrapper entrypoint is
"${CLAUDE_PLUGIN_ROOT}/.bin/codex-review". - The wrapper rebuilds the Go engine to
.bin/codex-review-go, walks a small parent-process chain to find the current Claude session file under~/.claude/sessions/, injects hidden--session-pidand--session-idruntime flags when available, and executes the binary from the workflow root when available. - The Go engine resolves the current Claude session and then resolves that session's workflow.
- If explicit runtime hints fail to resolve, the engine fails closed. It does not guess another workflow or fall back to another Claude session's plan.
planseeds the workflow from the current session's native Claude plan only when the canonicalartifacts/plan.mddoes not already exist, or when--planexplicitly replaces it.- Review rounds are forward-only:
__repeatincrements the round and runs another review__approveadvancesplan -> implementor completes the workflow
- Prior round artifacts are preserved.
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.
- 3d ago First seen · 88 lines · 1,034 tokens per session scan B 0a877186a80e
codex-review AGENTS.md is an instructions file published in the GitHub repository boyand/codex-review (16 stars, last pushed 17d ago), licensed MIT. It adds 1,034 tokens to every session, about $0.0052 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.