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/nytc69/review-loop/guidenpx skills add NYTC69/review-loop --skill guidegit clone --depth 1 https://github.com/NYTC69/review-loopWhat 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.00021 | $0.00589 |
| Opus 5 | $0.00010 | $0.00295 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
guide 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 2d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
review-loop Guide
What review-loop Does in Codex
In Codex Stage 1, review-loop is a repo skill that follows the same broad
review workflow used in Claude Code. It coordinates planning, implementation,
and review while keeping the shared session log current.
Codex Stage 1 follows the same broad exec -> polish -> docs -> security -> delivery lifecycle.
Codex reads and writes the same review-loop state as Claude Code:
.review-loop/config.md.review-loop/sessions/
That means a project can keep one shared config file and one shared session log history across both runtimes. Codex Stage 1 assumes a single orchestrator-owned workspace for the session.
Stage 1 Scope
Stage 1 in Codex includes only:
review-loopguide
It does not yet migrate:
code-quality-loopreview-prreorganize
Reviewer Behavior
Codex Stage 1 defaults to the outside-sandbox Claude CLI reviewer path. In
practice, that means review stays on claude -p --model ... unless the user
explicitly opts into the local Codex reviewer.
You can force the local Codex reviewer with:
codex_reviewer_backend: codex
This is the override to use when you want Codex to skip the Claude CLI reviewer
and use the Codex reviewer directly. In that case, codex_reviewer_model is
the paired model override, while reviewer_model still applies to the Claude
CLI reviewer path and judgment_model is its shared-tier fallback before the
explicit claude-sonnet-4-6 backstop.
cheap_model is accepted in the shared config so Claude and Codex can share
the same file, but in Codex Stage 1 it is a documented no-op because only
judgment-tier Codex agents are currently shipped.
quality_focus applies only when Step 3.5 Quality Polish actually runs.
skip_quality_polish: true mints polish as a no-op completion and still continues through docs and security.
Usage Notes
- Executor-created hidden worktrees are forbidden in Codex Stage 1.
- Codex Stage 1 supports
before-polish,before-docs, andbefore-securityas clean stop points. - Codex repo skills live under
.agents/skills/in the Codex workspace. - Keep the shared review-loop config in
.review-loop/config.md. - Keep session logs in
.review-loop/sessions/. - Use the local Codex reviewer only when you need to bypass the default Claude CLI reviewer path explicitly.
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.
- 2d ago First seen · 68 lines · 21 tokens per session scan A f7ca3330da84
guide is a skill published in the GitHub repository NYTC69/review-loop (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 21 tokens to every session and 589 once invoked, about $0.0001 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-31.
Other skills, from other repositories
codex-adversarial-review-lite
Codex Adversarial Review - Lite: user-invoked audit workflow for Claude Code users who want Codex CLI to independently review AI-generated code, plans, test expectations, and scope before fixes are applied. Cross-platform (Windows, macOS, Linux, WSL). Use only when the user explicitly invokes audit or selftest.
codex-handoff
Three-phase collaboration workflow between Claude Code (planner/decision-maker) and Codex CLI (implementer/reviewer) via the codex-plugin-cc plugin. Use whenever a coding task involves multiple files, new modules, cross-cutting refactors, business logic changes, or anything that warrants a written spec and a review…
brain-docs
Set up and maintain a "project brain" — a brain/ folder holding three living documents (decisions.md, flow.md, todo.md) that give a project persistent memory across chat sessions. Use this skill whenever the user wants a decision log, architecture/flow notes, project memory, living documentation, or notes that survive…
codex-handoff
Three-phase collaboration workflow between Claude Code (planner/decision-maker) and Codex CLI (implementer/reviewer) via the codex-plugin-cc plugin. Use whenever a coding task involves multiple files, new modules, cross-cutting refactors, business logic changes, or anything that warrants a written spec and a review…
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…