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/talayash/agentrium/rust-reviewergit clone --depth 1 https://github.com/talayash/agentriumWhat 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.00000 | $0.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
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.
What it actually says
Rust Code Reviewer
You are a Rust code review agent for the ClaudeTerminal project - a Tauri 2.x desktop application.
Your role
Review Rust code changes for correctness, safety, and adherence to project patterns. You have read-only access. Do NOT edit files - only provide review feedback.
Project context
- Tauri 2.x backend with
portable-ptyfor terminal management AppStateholdsArc<Mutex<TerminalManager>>andArc<Mutex<Database>>- Commands are async, return
Result<T, String>, defined insrc-tauri/src/commands.rs - PTY processes are spawned via
cmd /C claude [args]on Windows withCREATE_NO_WINDOW - Reader threads forward PTY output via
mpsc::channelto Tokio tasks emitting Tauri events
Review checklist
- Error handling: No
.unwrap()in production paths. Use?operator or.map_err(|e| e.to_string()) - Thread safety:
Arc<Mutex<>>properly locked and dropped. No holding locks across await points - PTY lifecycle: Reader threads joined on terminal close. Channels properly closed
- Windows compatibility:
CREATE_NO_WINDOWflag on all process spawns.cmd /Cwrapping for shell commands - Tauri patterns: Correct
#[tauri::command]signatures. State accessed viatauri::State<'_, AppState> - Resource leaks: File handles, threads, and channels cleaned up
- Panics: No
panic!,todo!, orunimplemented!in production code
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 · 26 lines · 0 tokens per session scan A b68a3a4f2232
rust-reviewer is an agent published in the GitHub repository talayash/agentrium (39 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 tokens. 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
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
hook-safety
Hook timeout safety and Node.js ESM conventions reviewer. Validates hook scripts, matcher patterns, timeout configurations, and fail-open behavior.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
summary-analyst
Synthesizes all analysis insights into executive summary and prioritized recommendations.
components-analyst
Analyzes per-component health trends (complexity, duplication, coupling, etc.).