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/akholod/consensus-review/loop-reviewgit clone --depth 1 https://github.com/akholod/consensus-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.00043 | $0.01238 |
| Opus 5 | $0.00022 | $0.00619 |
| Sonnet 5 | $0.00009 | $0.00248 |
| Haiku 4.5 | $0.00004 | $0.00124 |
Grade A, and why
loop-review 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 yesterday.
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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run the loop-review runtime and present its report.
What this is
/loop-review is the cheaper, sequential counterpart to /consensus-review. Where consensus-review runs a parallel panel of independent reviewers over the same change, loop-review builds the review context once and then makes several differentiated discovery passes over it, each told what is already covered and what is still open — but never told the previous pass's reasoning. That last part is the point: review models hyperfocus on one theme and miss what sits next to it, and persuasive context from an earlier pass makes the next one repeat it.
It reports; it never repairs
/loop-review finds problems and writes a report. It does not edit code, stage, commit, push,
or comment on a pull request — and that is enforced, not merely intended:
- every review pass is spawned with
--disallowed-toolscoveringEdit,Write,NotebookEdit,Bash,Task,Read,Grep,Glob,WebFetchandWebSearch, so the reviewing model holds no tool capable of changing anything; - the runtime contains no mutating
gitorghcommand.gh pr diffis the only forge call, and it reads; - its single write is the report file. Working files live in a temp directory outside the repo.
Applying fixes is a separate, human-initiated step. The intended cycle is: review → a human or a separate agent applies changes → review again on the new diff. The runtime recomputes the diff hash on every run, so a review of stale code cannot be mistaken for a review of the current one.
How to run it
node "${CLAUDE_PLUGIN_ROOT}/bin/loop-review.mjs" [flags]
| Flag | Meaning |
|---|---|
--pr=<n|url> |
Review a pull request (reuses the gh path; the fallback fetch stays in a temp dir) |
--range=<base..head> |
Review a git range |
| (neither) | Review uncommitted changes against HEAD |
--model=<m> |
Runner model (default sonnet) |
--timeout=<sec> |
Per-pass wall clock (default 240) |
--max-tokens=, --max-calls=, --max-ms= |
Hard budgets; exhausting one blocks CLEAN |
--out=<path> |
Report destination (default .reviews/loop-review-<hash>.md) |
--no-file |
Terminal only, no report written |
--json |
Emit the whole run state as JSON on stdout instead of the report |
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.
- yesterday First seen · 85 lines · 43 tokens per session scan A 7e6412fef8c1
loop-review is a command published in the GitHub repository akholod/consensus-review (3 stars, last pushed 12d ago), licensed MIT. It adds 43 tokens to every session and 1,238 once invoked, about $0.0002 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 commands, from other repositories
pi-code-review
Adversarial code review via Codex — break confidence in changes, not validate them.
pi-fact-check
Fact-check content via Gemini search + Claude verification — cross-provider claim validation.
pi-ui-review
UI/UX review via Gemini — accessibility, responsive design, component structure.
adversarial-review
Run an adversarial Gemini code review that challenges the implementation approach and design choices.
pi-askall
Ask both Codex and Gemini the same question — get three perspectives with Claude synthesis.
review
Run a standard Gemini code review of recent git changes.