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/checkgit 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/check)<a href="https://agentmods.dev/commands/s977043/river-review/check"><img src="https://agentmods.dev/badge/commands/s977043/river-review/check.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.00013 | $0.00243 |
| Opus 5 | $0.00006 | $0.00121 |
| Sonnet 5 | $0.00003 | $0.00049 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
check 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
対象プロジェクトに存在するチェックのみをこの順で実行して、失敗したら原因と修正案を出して：
- lint（
package.jsonにlintスクリプトがあればnpm run lint。なければプロジェクトの lint コマンドに読み替えるか省略する） - test（
package.jsonにtestスクリプトがあればnpm test。なければプロジェクトのテストコマンドに読み替えるか省略する）
注: このコマンドは Node プロジェクトの
npm run lint/npm testを想定しています。スクリプトが無い場合はMissing scriptエラーにせず、該当コマンドへ読み替えてください。
成功したら、変更の要点とリスクを 3 点でまとめて：
- 後方互換性
- 性能への影響
- セキュリティ考慮
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 · 17 lines · 13 tokens per session scan A df8e9ebc0db5
check is a command published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 13 tokens to every session and 243 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.