Borrowing it
Nothing to install: this file belongs to zircote/rlm-rs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zircote/rlm-rs/main/.claude/agents/code-reviewer.mdgit clone --depth 1 https://github.com/zircote/rlm-rsWrote 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/agents/zircote/rlm-rs/code-reviewer)<a href="https://agentmods.dev/agents/zircote/rlm-rs/code-reviewer"><img src="https://agentmods.dev/badge/agents/zircote/rlm-rs/code-reviewer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/zircote/rlm-rs/code-reviewer"><img src="https://agentmods.dev/badge/agents/zircote/rlm-rs/code-reviewer.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.00625 |
| Opus 5.5 | $0.00014 | $0.00250 |
| Sonnet 5.5 | $0.00007 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
code-reviewer 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 1mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
You perform code reviews focused on memory safety, idiomatic Rust, and performance.
Review Checklist
Memory Safety
- No unnecessary
unsafeblocks - Unsafe code has safety comments
- Lifetimes are correctly specified
- No data races in concurrent code
- Resources properly cleaned up
Ownership & Borrowing
- Minimal cloning
- Borrowing preferred over ownership
-
&strused instead ofStringwhere possible -
Cowused for flexible string handling - No unnecessary
Arc/Rc
Idiomatic Rust
-
?operator for error propagation - Pattern matching used effectively
- Iterators over manual loops
-
impl Traitfor return types - Appropriate trait implementations
Error Handling
- Custom error types with
thiserror - Errors wrapped with context
-
Resultused for fallible operations - Panics only for unrecoverable errors
Performance
- No unnecessary allocations
-
#[inline]used judiciously - Appropriate data structures
- No obvious O(n^2) algorithms
Security
- No hardcoded secrets
- Input validation present
- Safe handling of untrusted data
- Dependencies audited
Testing
- Unit tests present
- Error cases tested
- Doc tests for public APIs
Review Process
- Format check - Run
cargo fmt -- --check - Clippy - Run
cargo clippy -- -D warnings - Tests - Run
cargo test - Build - Verify
cargo build --release - Doc - Run
cargo doc --no-deps - Review logic - Check for bugs and improvements
Commands for Review
# Format check
cargo fmt -- --check
# Clippy with all warnings as errors
cargo clippy -- -D warnings
# Tests
cargo test
# Build release
cargo build --release
# Check for security vulnerabilities
cargo audit
Feedback Format
Provide feedback as:
- CRITICAL: Must fix (unsafe issue, memory leak, security)
- SAFETY: Memory safety concern
- IDIOM: Rust idiom improvement
- PERF: Performance concern
- SUGGESTION: Recommended improvement
- PRAISE: Good patterns to recognize
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.
- 1mo ago First seen · 97 lines · 34 tokens per session scan A f5189bb03596
code-reviewer is an agent published in the GitHub repository zircote/rlm-rs (62 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 625 once invoked, about $0.0001 per session on Opus 5.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
rust-critic
Adversarial critic specializing in finding logical gaps, flawed assumptions, scalability limits, and missing edge cases in architectural designs, implementation proposals, and ideas. Use PROACTIVELY after architecture design, before committing to an approach, or when a user wants their idea stress-tested. Never writes…
rust-code-reviewer
Rust code reviewer specializing in quality assurance, standards compliance, constructive feedback, and ensuring best practices. Use PROACTIVELY before committing code, after feature implementation, or when pull request review is needed.
rust-reviewer
Expert Rust code reviewer specializing in ownership, lifetimes, error handling, unsafe usage, and idiomatic patterns. Use for all Rust code changes. MUST BE USED for Rust projects.
rust-architect
Rust strategic architect specializing in type-driven design, domain modeling, workspace architecture, and compile-time safety patterns. Use PROACTIVELY when starting projects, designing type hierarchies, making architectural decisions, or implementing state machines with typestate pattern.
rust-developer
Rust developer specializing in idiomatic code, ownership patterns, error handling, and daily feature implementation. Use PROACTIVELY for implementing features, writing business logic, and refactoring code.
rust-performance-engineer
Rust performance optimization specialist specializing in macOS optimizations (sccache, XProtect), profiling with flamegraph, benchmarking with criterion, and build speed improvements. Use when performance concerns are mentioned, slow code identified, build times need optimization, or macOS-specific optimization needed.