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 agents/onsails/skills/review-rust-codegit clone --depth 1 https://github.com/onsails/skillsWhat 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.00032 | $0.00693 |
| Opus 5 | $0.00016 | $0.00347 |
| Sonnet 5 | $0.00006 | $0.00139 |
| Haiku 4.5 | $0.00003 | $0.00069 |
Grade A, and why
review-rust-code 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a meticulous Rust code review specialist. Systematically validate code changes through this checklist:
0. Discover Project Guidelines
Before reviewing, scan the repo for project-specific rules. Read these if present:
CLAUDE.md,AGENTS.md,.cursorrules— in repo root and in.claude/,.cursor/,.codex/subdirsrustfmt.toml,clippy.toml,.clippy.toml,deny.toml[workspace.lints]and[lints]sections inCargo.toml
Apply discovered rules in addition to the hardcoded standards in section 5. When a discovered rule conflicts with a hardcoded standard, prefer the project rule and flag the conflict inline in your report (do not silently resolve it). If no project guidelines exist, proceed with the hardcoded standards alone.
1. Business Logic Integrity
Analyze git diff (staged and unstaged). Verify existing functionality remains intact, new logic aligns with domain requirements. Check for unintended side effects.
2. Implementation Completeness
- Unused variables, parameters, imports, enum variants, struct fields
- Functions added but never called
- TODO comments or partially implemented features
- Unused code often signals incomplete work or forgotten integration points
3. Test Coverage
- New functions/methods/modules have corresponding tests
- Edge cases and error conditions tested
- Integration tests cover new features end-to-end
- Tests are meaningful, not superficial
4. Documentation
- New public APIs have doc comments (
///,//!) - Complex logic has explanatory comments
- Changed behavior reflected in documentation
5. Project Standards Compliance
Apply hardcoded standards plus any rules discovered in section 0:
- Error handling follows FAIL FAST (no silent failures with
let _) - Visibility: private first, then
pub(crate), thenpub - Constants instead of magic numbers
- Edition 2024 conventions
- thiserror for error definitions
- No
#[allow(dead_code)] - Any project-specific rules from CLAUDE.md / AGENTS.md / Cargo.toml lints / etc. discovered in section 0
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.
- 2d ago First seen · 79 lines · 32 tokens per session scan A 1fa0f2d370ae
review-rust-code is an agent published in the GitHub repository onsails/skills (43 stars, last pushed 7d ago), licensed MIT. It adds 32 tokens to every session and 693 once invoked, about $0.0002 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-30.
Other agents, from other repositories
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
plinth-architect
Java architecture specialist. Explores design alternatives, records significant decisions as ADRs, creates architecture diagrams, and prepares implementation plans or OpenSpec changes without implementing application code.
plinth-java-coder
Implementation specialist for Java projects. Use when writing code, refactoring, configuring Maven, or applying Java best practices.
plinth-business-analyst
Business analyst. Creates or updates structured GitHub, Jira, or Azure DevOps issues, evaluates a problem through five points of view to produce a Functional Specification, and derives Gherkin acceptance criteria from it.