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 instructions/s977043/river-review/agents-mdgit 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/instructions/s977043/river-review/agents-md)<a href="https://agentmods.dev/instructions/s977043/river-review/agents-md"><img src="https://agentmods.dev/badge/instructions/s977043/river-review/agents-md.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.01629 | $0.01629 |
| Opus 5 | $0.00814 | $0.00814 |
| Sonnet 5 | $0.00326 | $0.00326 |
| Haiku 4.5 | $0.00163 | $0.00163 |
Grade C, and why
river-review AGENTS.md scanned grade C with 2 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- Do not use destructive commands. The ban covers any command **you** run that rewrites already-pushed branch history (`git push --force` / `-f`, `git push --force-with-lease`) or discards work (`rm -rf`, `git reset --ha Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Do not make direct network calls (curl, wget, fetch) from scripts or code. Allowed CLI tools like `gh` are exempt. How it starts
The opening of the file, as written. The whole thing — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md—River Review
Scope
Canonical instructions for all AI coding agents in this repository.
Tool-specific files (CLAUDE.md, GEMINI.md, .codex/, copilot-instructions.md) contain only tool-specific policy and point here for repo-wide rules.
If a rule applies to all tools, it belongs in this file.
Repository Map
| Directory | Purpose |
|---|---|
skills/ |
Core review skills and registry content |
skills/agent-skills/ |
Packaged agent skills (SKILL.md + references/) |
src/ |
Runtime, CLI, and runner logic |
tests/ |
Node.js test suites |
pages/ |
Public docs; Japanese content is the source of truth |
docs/ |
Internal notes and runbooks; ask before editing |
runners/github-action/ |
GitHub Action runner implementation |
runners/node-api/ |
Separate TypeScript package (built with tsc) |
schemas/ |
JSON schemas for skills, output, and riverbed |
scripts/ |
Validation, evaluation, and build scripts |
Package Manager
Use npm.
| Task | Command |
|---|---|
| Install | npm install or npm ci |
| Lint | npm run lint |
| Test | npm test |
| Skills validation | npm run skills:validate |
| Agent skills validation | npm run agent-skills:validate |
| Agent definitions | npm run agents:validate |
| Local link check | npm run check:links:local |
| Docs dev server | npm run dev |
| Docs build | npm run build |
| TypeScript check | npm run build in runners/node-api/ (no root typecheck script) |
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 · 120 lines · 1,629 tokens per session scan C 5d2a8ef170a6
river-review AGENTS.md is an instructions file published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 1,629 tokens to every session, about $0.0081 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
logic-lens AGENTS.md
Instructions for hyhmrright/logic-lens, covering logic-lens — developer guide (codex cli), invoking skills, project layout, key conventions and no hooks.
adversarial-review AGENTS.md
Instructions for robertoecf/adversarial-review, covering agents.md: review agent guidelines (host-agnostic), plugin architecture, cross-host routing, anti-recursion contract and critique discipline (v0.8.1+).
adversarial-review CLAUDE.md
Instructions for robertoecf/adversarial-review, covering claude.md - claude code directives, plugin: adversarial-review v0.9.4, architecture, critical gotchas and tool preferences.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.