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/test-reviewgit clone --depth 1 https://github.com/akholod/consensus-reviewWrote 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/akholod/consensus-review/test-review)<a href="https://agentmods.dev/commands/akholod/consensus-review/test-review"><img src="https://agentmods.dev/badge/commands/akholod/consensus-review/test-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.00009 | $0.00184 |
| Opus 5 | $0.00005 | $0.00092 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
test-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 4d 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.
What it actually says
Run the test-reviewer subagent via Task and return its full structured result without abridgement.
subagent_type: "test-reviewer"(when installed as a plugin and the bare name does not resolve —consensus-review:test-reviewer)- Pass the scope from the args below into the prompt. Empty → tests related to the current working tree; a PR URL/ref → that PR; git range / path / glob — as given.
- Pass the output language if
lang=en|ua|ruis present (default English). - This is a read-only review: do not edit or commit anything. Stop after returning the result.
Scope: $ARGUMENTS
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.
- 4d ago First seen · 14 lines · 9 tokens per session scan A 221fa4fc7b10
test-review is a command published in the GitHub repository akholod/consensus-review (3 stars, last pushed 15d ago), licensed MIT. It adds 9 tokens to every session and 184 once invoked, about $0.0000 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
adversarial-review
Run an adversarial Gemini code review that challenges the implementation approach and design choices.
review
Run a standard Gemini code review of recent git changes.
logic-fix-all
Autonomous audit-and-fix — after consent, scan the target, fix every logic issue found (all severities), verify each fix, and report anything unresolved.
logic-diff
Check two code versions for semantic equivalence — use after a refactor or rewrite.
logic-explain
Trace execution step by step — use when code behavior is surprising or confusing.
logic-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.