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/s977043/river-review/prgit clone --depth 1 https://github.com/s977043/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/pr)<a href="https://agentmods.dev/commands/s977043/river-review/pr"><img src="https://agentmods.dev/badge/commands/s977043/river-review/pr.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.00015 | $0.00444 |
| Opus 5 | $0.00008 | $0.00222 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
pr 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
この差分を、以下のテンプレートで PR 本文にして。本文を確定する前に、末尾の「PR 説明と実態の突合チェック」を必ず実施する：
目的
（この変更で何を達成したいか）
変更点
（主な変更内容を箇条書きで）
動作確認
（どうテストしたか、確認コマンド）
影響範囲 / リスク
（破壊的変更、パフォーマンス、セキュリティ）
ロールバック手順
（問題発生時の戻し方）
本文を確定する前に、以下の「PR 説明と実態の突合チェック」を実施する。
- Closes/Fixes の突合 —
Closes #N/Fixes #Nを書く前にgh issue view Nで Issue の完了条件（受入条件・チェックリスト）を取得し、diff が各条件を満たすか 1 件ずつ突合する。未達の条件がある場合はClosesをRefsに変更するか、PR 本文に残課題として明記する。 - ja/en 対訳の同時更新 — ja/en 対訳ファイル（
*.mdと*.en.md、pages/配下の対）に触れた場合、両方が同一のコミットセットに含まれているか確認する。片側のみ更新する場合はその理由を本文に明記する。 - 本文と実 diff の最終セルフチェック — 本文の記述（「〜は変更しない」等の変更対象外の宣言、件数・列挙）が実 diff と矛盾しないか、
git diff --statと照合して確認する。
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 · 34 lines · 15 tokens per session scan A 658c05d39036
pr is a command published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 444 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
adversarial-review
Run an adversarial Gemini code review that challenges the implementation approach and design choices.
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.
logic-review
Review code for logic bugs — use when you suspect something is wrong but have no failing test yet.