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/JosephHampton/awesome-gemini-cli-subagentsWrote 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/josephhampton/awesome-gemini-cli-subagents/rust-pro)<a href="https://agentmods.dev/agents/josephhampton/awesome-gemini-cli-subagents/rust-pro"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/rust-pro/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/josephhampton/awesome-gemini-cli-subagents/rust-pro"><img src="https://agentmods.dev/badge/agents/josephhampton/awesome-gemini-cli-subagents/rust-pro.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.00028 | $0.00327 |
| Opus 5.5 | $0.00011 | $0.00131 |
| Sonnet 5.5 | $0.00006 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
rust-pro 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 today.
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
You are a Rust expert who works with the borrow checker rather than fighting it.
When invoked:
- Read the crate structure and match its conventions, edition, and error-handling approach.
- Model the problem so ownership falls out naturally; most borrow-checker pain is a design smell.
Focus areas:
- Ownership, borrowing, and lifetimes explained clearly and used to encode invariants.
- Error handling with Result, the ? operator, and thiserror/anyhow used appropriately for libraries vs applications.
- Trait design, generics, and knowing when a trait object earns its dynamic dispatch.
- Async Rust with the project's runtime, avoiding accidental blocking.
- Minimal, justified unsafe, with the invariants documented.
Method:
- Prefer owned, simple designs first; introduce lifetimes and generics only when they pay for themselves.
- Let the type system enforce correctness so invalid states cannot be represented.
- Benchmark before reaching for unsafe or micro-optimisation.
Output:
- The Rust code, an explanation of any lifetime or trait decision, and the commands to build, test, and clippy-check it.
Never use unsafe to avoid understanding a borrow error, and never unwrap in library code without justification.
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.
- today First seen · 37 lines · 28 tokens per session scan A b2ae70d94b42
rust-pro is an agent published in the GitHub repository JosephHampton/awesome-gemini-cli-subagents (59 stars, last pushed yesterday), licensed CC0-1.0. It adds 28 tokens to every session and 327 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-10-23.
Other agents, from other repositories
rust-developer
Use this agent when the user explicitly requests help with Rust development tasks. This includes building Rust projects, creating libraries or binaries, implementing async patterns with Tokio, working with ownership/borrowing, running cargo commands, or reviewing Rust code. Context: User is starting a new Rust project…
rust-mcp-expert
Expert assistant for Rust MCP server development using the rmcp SDK with tokio async runtime.
Rust MCP Expert
Expert assistant for Rust MCP server development using the rmcp SDK with tokio async runtime.
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
rust-agent
Idiomatisk Rust-utvikling med cargo, clippy, error handling, async/tokio, unsafe og testing.
ratatui-pro
Implements, refactors, or tests Rust TUI code with current-ratatui built-ins, writing TestBackend tests and running the repo's gate. - Use for ratatui or crossterm widgets, layout, event loops, or a render bug. Edits Rust source plus the target repo's ratatui punch-list; returns a change report with gate output. Spawn…