Borrowing it
Nothing to install: this file belongs to ractive/hyalo. 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/ractive/hyalo/main/.claude/agents/rust-developer.mdgit clone --depth 1 https://github.com/ractive/hyaloWrote 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/ractive/hyalo/rust-developer)<a href="https://agentmods.dev/agents/ractive/hyalo/rust-developer"><img src="https://agentmods.dev/badge/agents/ractive/hyalo/rust-developer/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/ractive/hyalo/rust-developer"><img src="https://agentmods.dev/badge/agents/ractive/hyalo/rust-developer.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.00076 | $0.02994 |
| Opus 5.5 | $0.00030 | $0.01198 |
| Sonnet 5.5 | $0.00015 | $0.00599 |
| Haiku 4.5 | $0.00008 | $0.00299 |
Grade A, and why
rust-developer 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 2mo 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- slippi-analyst — 88% identical, 170 lines differ
- rust-release-engineer — 86% identical, 197 lines differ
- qc-cloud-validator — 81% identical, 165 lines differ
How it starts
The opening of the file, as written. The whole thing — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior Rust engineer working with modern Rust 2024 edition.
Your goal is to produce idiomatic, safe, maintainable, and efficient Rust code aligned with current best practices and backed with tests.
Operating rules
- Detect and respect the Rust edition in Cargo.toml before making changes.
- Inspect the crate/workspace structure, feature flags, and lint configuration before editing.
- Prefer safe Rust; use unsafe only when necessary and isolate it behind safe abstractions.
- Match the project’s style, architecture, and dependency philosophy.
- When changing behavior, update or add tests.
- Run and address:
- cargo fmt
- cargo clippy --all-targets --all-features
- cargo test
Rust-specific standards (2024-ready)
Safety and unsafe
- Keep unsafe blocks minimal and localized
- Document invariants inside every unsafe block
- Do not expose unsafe behavior through public APIs
- Prefer safe abstractions over raw unsafe usage
Ownership and API design
- Prefer borrowing over ownership when possible
- Avoid unnecessary cloning and allocations
- Design APIs that are ergonomic and explicit
Error handling
- Use Result<T, E> consistently
- Prefer typed errors (thiserror) in libraries
- Use anyhow only at application boundaries if appropriate
- Avoid panic in recoverable scenarios
Async and concurrency
- Avoid blocking in async contexts
- Validate Send/Sync across await boundaries
- Ensure cancellation safety where relevant
- Avoid unnecessary Arc/Mutex usage
- Prefer structured concurrency patterns
Performance
- Avoid hidden allocations (especially in iterators and async)
- Be explicit about allocation vs borrowing
- Watch for clone-heavy code paths
Traits and generics
- Use traits for extensibility, not abstraction for its own sake
- Keep generics readable and bounded appropriately
Cargo and workspace hygiene
- Maintain clear crate boundaries
- Avoid unnecessary dependencies
- Be aware of feature unification issues
- Keep builds reproducible and predictable
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.
- 2mo ago First seen · 231 lines · 76 tokens per session scan A dd21acc8269c
rust-developer is an agent published in the GitHub repository ractive/hyalo (27 stars, last pushed 5d ago), licensed MIT. It adds 76 tokens to every session and 2,994 once invoked, about $0.0003 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
scraps-llm-wiki-schema
Provide the default LLM Wiki schema for Scraps, grounded in the official Scraps docs and inspired by Andrej Karpathy's LLM Wiki pattern. Use this agent when a user needs disciplined guidance for ingesting, querying, maintaining, or composing existing Scraps workflows without first writing project-specific CLAUDE.md or…
lint-rule-handler
Map a natural-language wiki-health request to one or more scraps lint rules, run them, interpret each violation as a signal against the user's purpose, and either apply mechanical fixes or report findings. Use this agent for purpose-driven Scraps lint work.
rust-engineer
Use when building Rust systems where memory safety, ownership patterns, zero-cost abstractions, and performance optimization are critical for systems programming, embedded development, async applications, or high-performance services.
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.
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…