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 rules/s977043/river-review/cursorrulesgit 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/rules/s977043/river-review/cursorrules)<a href="https://agentmods.dev/rules/s977043/river-review/cursorrules"><img src="https://agentmods.dev/badge/rules/s977043/river-review/cursorrules.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.00231 | $0.00231 |
| Opus 5 | $0.00115 | $0.00115 |
| Sonnet 5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
cursorrules 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 today.
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
River Reviewer — Cursor Agent Rules
Prerequisites: river CLI must be installed globally and available in Cursor's terminal PATH.
npm i -g @s977043/river-review
Verify: river --version
If 'command not found' occurs, install via the command above or follow the quickstart guide:
https://river-reviewer.s977043.dev/docs/quickstart
When to run River Reviewer
- Before committing: run a code review on staged changes.
- When the user asks to "review", "check", or "audit" the current diff or a file.
Command
river run . --reviewers auto
If no API key is configured, use dry-run mode to validate the setup without making API calls:
river run . --dry-run
Interpreting results
- Critical / Major: Block the commit or merge. Explain the issue to the user and suggest a fix.
- Minor: Advisory. Surface to the user but do not block.
- Info: Informational only.
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.
- today First seen · 31 lines · 231 tokens per session scan A e9e456cd89af
cursorrules is a cursor rule published in the GitHub repository s977043/river-review (3 stars, last pushed today), licensed MIT. It adds 231 tokens to every session, about $0.0012 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-09-03.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.