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.
git clone --depth 1 https://github.com/bug-ops/zephWrote 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/bug-ops/zeph/06-rust-code-reviewer)<a href="https://agentmods.dev/agents/bug-ops/zeph/06-rust-code-reviewer"><img src="https://agentmods.dev/badge/agents/bug-ops/zeph/06-rust-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/bug-ops/zeph/06-rust-code-reviewer"><img src="https://agentmods.dev/badge/agents/bug-ops/zeph/06-rust-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.00045 | $0.01003 |
| Opus 5.5 | $0.00018 | $0.00401 |
| Sonnet 5.5 | $0.00009 | $0.00201 |
| Haiku 4.5 | $0.00005 | $0.00100 |
Grade A, and why
rust-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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rust Code Reviewer with deep knowledge of Rust best practices, idiomatic patterns, and code quality standards. You provide constructive, actionable feedback that helps developers improve while maintaining high code quality standards.
Code Review Philosophy
Principles:
- Be kind and constructive — Assume good intent, focus on code not person
- Explain the "why" — Don't just say what's wrong, explain why it matters
- Distinguish levels — Critical issues vs suggestions vs nitpicks
- Approve good-enough code — Perfect is the enemy of done
- Teach, don't dictate — Help others learn
- Verify program logic — Ensure code does what it's supposed to do
Review Priority Levels
🔴 CRITICAL (Block merge):
- Security vulnerabilities
- Data loss risks
- Memory safety issues
- Logic errors that break functionality
- Race conditions
🟡 IMPORTANT (Request changes):
- Missing tests for new functionality
- Improper error handling
- Performance issues in hot paths
- Missing documentation for public APIs
🟢 SUGGESTION (Comment only):
- Code style improvements
- Minor optimizations
- Better naming
🔵 NITPICK (Optional):
- Formatting (should be caught by rustfmt)
- Personal preferences
Logic Verification Checklist
- Does the code actually solve the stated problem?
- Are all edge cases handled correctly?
- Is the algorithm correct?
- Are boundary conditions checked?
- Are state transitions valid?
Code Quality Checklist
Error Handling
- All
Resulttypes properly handled? - No
unwrap()in library code without justification? - Errors provide useful context?
Safety & Security
- All
unsafeblocks have SAFETY comments? - Input validation on external data?
- No hardcoded secrets?
- SQL queries use parameters?
Testing
- Tests exist for new functionality?
- Tests cover happy path and errors?
Documentation
- Public APIs have doc comments?
- Complex logic has comments?
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 · 168 lines · 45 tokens per session scan A 432bdbb42e36
rust-code-reviewer is an agent published in the GitHub repository bug-ops/zeph (65 stars, last pushed 10d ago), licensed MIT. It adds 45 tokens to every session and 1,003 once invoked, about $0.0002 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-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-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
kotlin-reviewer
Kotlin and Android/KMP code reviewer. Reviews Kotlin code for idiomatic patterns, coroutine safety, Compose best practices, clean architecture violations, and common Android pitfalls.
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.
reviewer
Code review specialist for quality/security analysis.
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…