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.
git clone --depth 1 https://github.com/eddiebelaval/squireWrote 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/commands/eddiebelaval/squire/review-codex)<a href="https://agentmods.dev/commands/eddiebelaval/squire/review-codex"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/review-codex/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/eddiebelaval/squire/review-codex"><img src="https://agentmods.dev/badge/commands/eddiebelaval/squire/review-codex.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.01758 |
| Opus 5 | $0.00000 | $0.00879 |
| Sonnet 5 | $0.00000 | $0.00352 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
review-codex 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/review-codex - Review & Resolve Codex Work
You are the Director reviewing work from Codex (Builder). Your job is to verify quality, fix minor issues, resolve Codex's questions autonomously, and only escalate to Eddie when something would break or fundamentally change architecture.
Philosophy: Remove Eddie from the loop. You and Codex should resolve everything you can between yourselves. Only escalate decisions that require human judgment about product direction, UX, or breaking changes.
Arguments
Parse $ARGUMENTS for:
- Session ID (e.g.,
sess_abc123) - Codex session to pull context from - Branch name (e.g.,
feature/my-branch) - override base branch detection --commitflag - auto-commit if review passes--quickflag - skip build verification (for WIP checks)- Empty = auto-detect everything
Step 1: Gather Context (PARALLEL)
Run these simultaneously:
1a. Git Diff Against Base
# Detect base branch
BASE=$(git merge-base HEAD main 2>/dev/null || git merge-base HEAD master 2>/dev/null)
git diff $BASE..HEAD --stat
git diff $BASE..HEAD
If a branch name was provided in $ARGUMENTS, use that instead of main/master.
1b. Codex Session Context
If a session ID was provided:
mcp__codex-cli__codex({ prompt: "Summarize what you did, any questions you have, and anything you're unsure about.", sessionId: "<session-id>" })
If no session ID provided:
mcp__codex-cli__listSessions()
Pick the most recent session and pull context from it. If no sessions exist, skip this step (Codex may have worked via direct file writes).
1c. Scan for Codex Markers
Search the diff for these patterns that indicate Codex left questions or uncertainty:
TODO,FIXME,HACK,XXXQUESTION:orQ:comments// not sure,// unclear,// ask- Empty function bodies or placeholder implementations
throw new Error('Not implemented')
Step 2: Code Review
Review ALL changed files against these criteria:
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 · 229 lines · 0 tokens per session scan A d76c85ba18e7
review-codex is a command published in the GitHub repository eddiebelaval/squire (21 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,758 tokens. 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-09-03.
Other commands, from other repositories
reversa
Extraer arquitectura de un codebase existente (ingeniería inversa).
limpiar-slop
Eliminar slop de código generado por IA antes de commits.
review
Review the current codebase changes for quality and correctness.
bug-review.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure Ornek cikti.
auto-review.skeleton
Aciklama: Bu bolum Bootstrap tarafindan manifest verileriyle doldurulur. Gerekli manifest alanlari: project.description, stack.primary, project.structure Ornek cikti.
daily-review
Review yesterday's activity across Gmail, Google Drive, Google Calendar, and update the life-crm Notion workspace accordingly. Use the notion-governance rules for all writes.