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/wallneradam/cc-plugin-counterpointWrote 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/wallneradam/cc-plugin-counterpoint/review_loop)<a href="https://agentmods.dev/commands/wallneradam/cc-plugin-counterpoint/review_loop"><img src="https://agentmods.dev/badge/commands/wallneradam/cc-plugin-counterpoint/review_loop/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/wallneradam/cc-plugin-counterpoint/review_loop"><img src="https://agentmods.dev/badge/commands/wallneradam/cc-plugin-counterpoint/review_loop.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.00024 | $0.04348 |
| Opus 5.5 | $0.00010 | $0.01739 |
| Sonnet 5.5 | $0.00005 | $0.00870 |
| Haiku 4.5 | $0.00002 | $0.00435 |
Grade C, and why
review_loop scanned grade C 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 1mo 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
**Wipe old runs at start — but never with a variable-glob `rm`.** Before creating the new run directory, delete every existing entry directly under `counterpoint-review-loop/`, nothing outside it. Do NOT write `rm -rf "$ How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Counterpoint Review Loop
Run an autonomous loop around the counterpoint review mode: review → verify each finding → fix the real ones → report back to Codex → re-review, until Codex approves or a safety cap is hit.
Parse --scope, --base, --path (repeatable), and --effort from $ARGUMENTS and pass them through to every review round. If the user names files or directories without flags, treat them as --path arguments.
What makes this loop different from re-running one-shot reviews: every iteration continues the same persistent Codex thread. Codex remembers its own findings by id, verifies claimed fixes in the actual code, and updates each finding's status (resolved / still-open / revised / withdrawn). A false positive rejected once stays withdrawn — it is never re-litigated. This makes convergence fast; most runs finish in 2–5 iterations.
Mindset: Codex is one reviewer, not the source of truth
Codex findings are hypotheses. Every finding must be verified against the actual code before any fix is applied — false positives are routine, and applying them blindly makes the code worse. Disagreeing with Codex is fine and often correct: if a finding contradicts project conventions (CLAUDE.md / AGENTS.md), if the flagged behavior is intentional, or if the claim simply does not hold, classify it as a false positive and push back in the next round so Codex withdraws it.
Architecture: orchestrator + per-iteration sub-agents
Do not run the whole loop inside one agent — a long loop accumulates context and degrades. The split is strict:
The orchestrator (you, the agent running this command):
- Prepares the workspace (see below).
- Spawns ONE per-iteration sub-agent at a time via the
Agenttool, synchronously: passrun_in_background: falseEXPLICITLY,subagent_type: "general-purpose". Newer harnesses run agents in the background BY DEFAULT — omitting the flag detaches the worker, the orchestrator's turn ends, and the completion notification may never arrive, silently stalling the loop. A synchronous Agent call blocks and returns the worker's final JSON inline; a sub-agent taking 5–10+ minutes is normal — wait for it. - Reads each sub-agent's JSON summary (returned as final message and written to
iteration-NN.json). - Decides continue/stop per the convergence rules.
- Prints EXACTLY the per-iteration progress output defined below — one stats line plus the worker's 1–3 sentence summary, nothing more — and, at the end, writes
final-summary.mdplus a 2–3 line closing summary.
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.
- 1mo ago First seen · 253 lines · 24 tokens per session scan C 606e74ad12f9
review_loop is a command published in the GitHub repository wallneradam/cc-plugin-counterpoint (2 stars, last pushed 1mo ago), licensed MIT. It adds 24 tokens to every session and 4,348 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
refactor
Systematic code refactoring with smart scope detection.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
boot
Start a new PromptKit prompt assembly session (alias for /bootstrap).
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.