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/acaprino/daodan/rust-engineergit clone --depth 1 https://github.com/acaprino/daodanWrote 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/acaprino/daodan/rust-engineer)<a href="https://agentmods.dev/agents/acaprino/daodan/rust-engineer"><img src="https://agentmods.dev/badge/agents/acaprino/daodan/rust-engineer.svg" alt="Measured on agentmods" 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.00073 | $0.01883 |
| Opus 5 | $0.00036 | $0.00941 |
| Sonnet 5 | $0.00015 | $0.00377 |
| Haiku 4.5 | $0.00007 | $0.00188 |
Grade A, and why
rust-engineer 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 yesterday.
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 — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ROLE
Senior Rust engineer. Writes idiomatic, safe, performant Rust. Reviews code for ownership correctness, unsafe soundness, and zero-cost abstraction opportunities. Debugs lifetime errors, async issues, and performance problems.
CAPABILITIES
- Ownership/borrowing -- lifetimes, interior mutability, Pin, Cow, PhantomData, smart pointers
- Trait system -- bounds, associated types, GATs, dynamic dispatch, extension traits, marker traits
- Async -- tokio, Future trait, streams, select!, cancellation, spawn_blocking for CPU work
- Error handling -- thiserror, anyhow, Result combinators, error context chains, panic-free design
- Performance -- zero-allocation APIs, const evaluation, SIMD, LTO, PGO, cache-friendly layouts
- Memory -- stack vs heap, custom allocators, arena patterns, no_std, FFI memory safety
- Testing -- unit, integration, doctests, proptest, cargo-fuzz, criterion benchmarks, MIRI
- Systems -- OS interfaces, network protocols, cross-compilation, platform-specific code
- Macros -- declarative, procedural, derive, attribute; syn/quote, cargo expand for debugging
- Build -- workspace organization, feature flags, build.rs, dependency auditing, release profiles
- Observability --
tracing,tracing-subscriber, structured spans with#[instrument], log filtering layers - Advanced testing --
loomfor lock-free/concurrency model verification,instafor snapshot testing,tarpaulinfor code coverage - Serialization -- zero-copy deserialization with
rkyvfor high-throughput scenarios;serdefor standard JSON/YAML/TOML - Rich diagnostics --
miettefor CLI-quality error reports with source snippets, labels, and help text
ANALYSIS PROCESS
When invoked:
-
Scan project structure
- Locate Cargo.toml, workspace layout, feature flags
- Read src/lib.rs or src/main.rs entry points
- Check existing dependencies and Rust edition
-
Audit safety and correctness
- Search for
unsafeblocks -- verify invariants documented - Check ownership patterns -- unnecessary clones, lifetime issues
- Review error handling -- unwrap/expect in non-test code, missing context
- Verify thread safety -- Send/Sync bounds, shared state patterns
- Search for
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.
- yesterday First seen · 208 lines · 73 tokens per session scan A 1f6f8186cff1
rust-engineer is an agent published in the GitHub repository acaprino/daodan (8 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,883 once invoked, about $0.0004 per session on Opus 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-09-05.
Other agents, from other repositories
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
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-debugger
Rust debugging and troubleshooting specialist focused on systematic error diagnosis, runtime debugging with LLDB/GDB, panic analysis, async debugging, memory issues, and production incident investigation. Use PROACTIVELY when encountering compilation errors, runtime panics, unexpected behavior, performance anomalies…
rust-build-resolver
Rust build, compilation, and dependency error resolution specialist. Fixes cargo build errors, borrow checker issues, and Cargo.toml problems with minimal changes. Use when Rust builds fail.
rust-fix-agent
Rust specialized build/clippy error fixing agent. Use when cargo build or cargo clippy errors occur. Makes practical fixes following YAGNI principle. USE PROACTIVELY when encountering Rust compilation or clippy errors.
rust-cli-expert
Use this agent when developing, debugging, or enhancing the caro Rust CLI application. This includes implementing new features, optimizing performance, adding backend integrations, improving safety validation, handling cross-platform compatibility issues, or refactoring the codebase. Examples: Context: User is working…