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/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/impact-review)<a href="https://agentmods.dev/commands/akholod/consensus-review/impact-review"><img src="https://agentmods.dev/badge/commands/akholod/consensus-review/impact-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.1 | $0.00016 | $0.00191 |
| Opus 5 | $0.00008 | $0.00096 |
| Sonnet 5 | $0.00003 | $0.00038 |
| Haiku 4.5 | $0.00002 | $0.00019 |
Grade A, and why
impact-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 6d 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 impact-reviewer subagent via Task and return its full structured result without abridgement (starting with the one-line verdict).
subagent_type: "impact-reviewer"(when installed as a plugin and the bare name does not resolve —consensus-review:impact-reviewer)- Pass the scope from the args below into the prompt. Empty → current working tree (staged + unstaged); a PR URL/ref → that PR (all commits against base).
- 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.
- 6d ago First seen · 14 lines · 16 tokens per session scan A 013bbb18697d
impact-review is a command published in the GitHub repository akholod/consensus-review (3 stars, last pushed 18d ago), licensed MIT. It adds 16 tokens to every session and 191 once invoked, about $0.0001 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
merge-check
A pre-merge checklist command for a GitHub pull request. A pull request is a proposed code change, and the command checks whether it meets the project’s documented requirements before merging.
release-kick
A release command for the River Review project that checks release instructions and pull-request state, updates an out-of-date branch, and verifies the release after merging.
plan-merge-order
A command that plans the order for merging several pull requests (PRs), which are proposed code changes reviewed before entering a shared branch. It checks their status and file changes, then studies dependencies and overlap to reduce rebasing work.
preflight
A pre-work check for finding whether a coding task or pull request is already finished, obsolete, or being handled elsewhere. A pull request is a proposed change to a code repository.
register-plugin-asset
A project command for adding a distributable command, agent, or agent skill to a plugin manifest, the file that lists what a plugin provides.
verify-agent-report
A command for checking whether an agent’s reported branch, pull request, commit, or files actually exist. A pull request is a proposed code change submitted for review.