Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add s977043/river-review/plugin install river-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/s977043/river-review/readme)<a href="https://agentmods.dev/commands/s977043/river-review/readme"><img src="https://agentmods.dev/badge/commands/s977043/river-review/readme.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.00000 | $0.00477 |
| Opus 5 | $0.00000 | $0.00238 |
| Sonnet 5 | $0.00000 | $0.00095 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
README 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 5d 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
.claude/commands/ (repo-dev commands)
Repo-development slash commands (NOT part of the distributed plugin surface).
| Command | File | Purpose |
|---|---|---|
/propose-issue |
propose-issue.md |
Research codebase before creating an issue, then fact-check the issue body's claims |
/plan-merge-order |
plan-merge-order.md |
Plan merge order for multiple PRs to minimize rebase cost |
/preflight |
preflight.md |
Verify tasks are not obsolete or in parallel before work |
/verify-agent-report |
verify-agent-report.md |
Verify agent completion reports against real branches, PRs, and commits |
/merge-check |
merge-check.md |
Run the pre-merge checklist (docs/governance.md) against a PR number |
/register-plugin-asset |
register-plugin-asset.md |
Register a new distributed command/agent/agent-skill into the plugin manifests and validate |
/release-kick |
release-kick.md |
Drive a release-please PR from BLOCKED unblock through merge and release verification |
配布対象のコマンドは #996 で top-level
commands/へ分離し、.claude-plugin/plugin.jsonがそこを参照します。一覧はdocs/development/distributed-commands.mdが正で、本ディレクトリには repo-dev 専用コマンドのみが残ります。整合性: コマンド追加時は配布対象か repo-dev かを判断して正しい場所に置き、CLAUDE.md の
Custom Commands表を更新すること。配布対象コマンドの場合はさらに.claude-plugin/plugin.jsonのcommandsにも追加する必要があります。上の表と.claude/commands/*.mdの一致はnpm run check:doc-enum（meta:validate経由で CI 必須チェック）が機械検証します。
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.
- 5d ago First seen · 18 lines · 0 tokens per session scan A 8482ee9ad555
README is a command published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 477 tokens. 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
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-health
Sweep a whole codebase or directory for logic correctness — use before a release or to identify risk hotspots.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.
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.
consensus-review
Consensus code review (Opus arbiter + codex, optional pi advisor) across 4 dimensions (architecture/quality/impact/tests) for a PR or uncommitted changes; P0–P2 findings; strict sceptic by default; every flag also accepted with a leading -.