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 commands/dkorobtsov/codex-review-loop/cancel-reviewgit clone --depth 1 https://github.com/dkorobtsov/codex-review-loopWrote 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/dkorobtsov/codex-review-loop/cancel-review)<a href="https://agentmods.dev/commands/dkorobtsov/codex-review-loop/cancel-review"><img src="https://agentmods.dev/badge/commands/dkorobtsov/codex-review-loop/cancel-review.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.00006 | $0.00183 |
| Opus 5 | $0.00003 | $0.00092 |
| Sonnet 5 | $0.00001 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade B, and why
cancel-review 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.
- Bash(cat .claude/codex-review-*.local.md *) What it actually says
Check if any review loops are active:
ls .claude/codex-review-*.local.md 2>/dev/null && echo "ACTIVE" || echo "NONE"
If active, read each state file to show phase and review ID.
Then remove all state files:
rm -f .claude/codex-review-*.local.md
Report: "Review loop(s) cancelled" with the phase and review ID of each.
If no review loops were active, report: "No active review loops found."
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 · 27 lines · 6 tokens per session scan B b8b3cad7cec2
cancel-review is a command published in the GitHub repository dkorobtsov/codex-review-loop (2 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 183 once invoked, about $0.0000 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.