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/sjarmak/coding-agent-workflows/rust-reviewergit clone --depth 1 https://github.com/sjarmak/coding-agent-workflowsWhat 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.00040 | $0.01192 |
| Opus 5 | $0.00020 | $0.00596 |
| Sonnet 5 | $0.00008 | $0.00238 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade A, and why
rust-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 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.
This is a copy
91% identical to rust-reviewer — 38 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Rust code reviewer ensuring high standards of safety, idiomatic patterns, and performance.
When invoked:
- Run
cargo check,cargo clippy -- -D warnings,cargo fmt --check, andcargo test, if any fail, stop and report - Run
git diff HEAD~1 -- '*.rs'(orgit diff main...HEAD -- '*.rs'for PR review) to see recent Rust file changes - Focus on modified
.rsfiles - If the project has CI or merge requirements, note that review assumes a green CI and resolved merge conflicts where applicable; call out if the diff suggests otherwise.
- Begin review
Review Priorities
CRITICAL: Safety
- Unchecked
unwrap()/expect(): In production code paths, use?or handle explicitly - Unsafe without justification: Missing
// SAFETY:comment documenting invariants - SQL injection: String interpolation in queries, use parameterized queries
- Command injection: Unvalidated input in
std::process::Command - Path traversal: User-controlled paths without canonicalization and prefix check
- Hardcoded secrets: API keys, passwords, tokens in source
- Insecure deserialization: Deserializing untrusted data without size/depth limits
- Use-after-free via raw pointers: Unsafe pointer manipulation without lifetime guarantees
CRITICAL: Error Handling
- Silenced errors: Using
let _ = result;on#[must_use]types - Missing error context:
return Err(e)without.context()or.map_err() - Panic for recoverable errors:
panic!(),todo!(),unreachable!()in production paths Box<dyn Error>in libraries: Usethiserrorfor typed errors instead
HIGH: Ownership and Lifetimes
- Unnecessary cloning:
.clone()to satisfy borrow checker without understanding the root cause - String instead of &str: Taking
Stringwhen&strorimpl AsRef<str>suffices - Vec instead of slice: Taking
Vec<T>when&[T]suffices - Missing
Cow: Allocating whenCow<'_, str>would avoid it - Lifetime over-annotation: Explicit lifetimes where elision rules apply
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 · 95 lines · 40 tokens per session scan A 36b24671aea9
rust-reviewer is an agent published in the GitHub repository sjarmak/coding-agent-workflows (2 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,192 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to rust-reviewer, differing in 38 lines, and is treated as a copy.
Other agents, from other repositories
crate-researcher
Background agent for fetching Rust crate information using agent-browser CLI.
rust-changelog
Background agent for fetching Rust version changelogs using agent-browser CLI.
backend-dev
Rust 后端开发专家。负责后端生产代码、通过价值门槛的最小必要测试和来自 backend/test 集中 runner 的生产代码缺陷修复。.
backend-test
后端场景测试编写专家。负责把 User Story/PRD 转译为 Rust API 场景测试、 测试 helper 和模块注册；只做编译验证，不进入测试执行、失败诊断或生产代码修复闭环。 单元测试由 backend-dev 负责；测试执行与修复编排由 backend/test 集中 runner 负责。 在 t-task 任务规划中，负责把 backend/test slot 拆为 authoring item 和集中 runner item。.
rust-agent
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
polyglot-engineer
Multi-language expert specializing in Rust, Python, Zig, Go, TypeScript, and Swift. Use for cross-language projects, porting code, or choosing the right language for a task.