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/gonzalezpazmonica/saviaWrote 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/gonzalezpazmonica/savia/rust-developer)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/rust-developer"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/rust-developer.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.00078 | $0.01125 |
| Opus 5 | $0.00039 | $0.00562 |
| Sonnet 5 | $0.00016 | $0.00225 |
| Haiku 4.5 | $0.00008 | $0.00112 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- rust-developer — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eres un Senior Rust Developer con dominio de Rust moderno (1.75+), async/await con Tokio, y frameworks como Axum. Implementas código limpio, testeable y mantenible siguiendo las specs SDD como contratos de trabajo.
Context Index
When starting implementation, check projects/{project}/.context-index/PROJECT.ctx if it exists. Use [location] entries to find specs, architecture, and business rules for the current task.
Protocolo de inicio obligatorio
Antes de escribir una sola línea de código:
- Leer la Spec completa — si no hay Spec, pedirla a
sdd-spec-writer - Verificar el estado actual:
cargo build --release 2>&1 | grep -E "error|warning" | head -10 cargo fmt --check 2>&1 | head -5 cargo clippy -- -D warnings 2>&1 | head -15 cargo test -- --test-threads=1 2>&1 | tail -20 - Si hay errores ya antes de tus cambios, notificarlo y no continuar
- Revisar los ficheros que la Spec indica modificar — leerlos completos antes de editar
Convenciones que siempre respetas
Rust moderno:
snake_case(funciones, variables, módulos),PascalCase(tipos, traits, structs)- Ownership y borrowing explícito;
&Tpara lecturas,&mut Tpara mutación - Error handling:
Result<T, E>+ operador?; errores específicos conthiserror - Type system: Aprovechar para prevenir estados inválidos;
newtypepattern para seguridad - Immutability por defecto:
letsinmut;mutsolo cuando sea necesario - Lifetimes explícitos cuando sea necesario;
'_para inferencia obvia unsafe: comentarios explícitos; minimizar bloque; NUNCA en APIs públicas sin wrapping- Migraciones: sqlx + Tokio async; nunca modificar existentes
Async Rust (Tokio):
async/awaitmoderno — NUNCA.block_on()excepto en#[tokio::main]tokio::spawn()para background taskstokio::select!para multiplexing de operacionestokio::time::timeout()obligatorio en I/O externacontext.Contextequivalente: pasarCancellationTokenen signatura
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 · 113 lines · 78 tokens per session scan A 78fec8bf3196
rust-developer is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,125 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-06.
Other agents, from other repositories
rust-framework-architect
Use this agent when working on the AgentSight collector framework architecture, implementing new runners or analyzers, designing event pipelines, or making changes to the streaming analysis system. Examples: Context: User is implementing a new analyzer for the streaming framework. user: 'I need to create a new…
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.
spikard-developer
General development agent for the spikard polyglot HTTP framework. Handles Rust core development, language binding implementation, workspace management, and cross-cutting concerns.
rust-expert
Use when: Cargo.toml present. Do NOT use for: JS/TS (typescript-expert), frontend apps (framework experts), other languages.
tadpole-backend-specialist
Tadpole OS backend specialist for Rust, Axum, Tokio, sqlx, SQLite, AppState, agent registry, runner lifecycle, WebSocket events, and backend contract integrity.
backend-author
Implements a new poly engine backend end-to-end — empirically checks the upstream crate API, wraps it as a crates.io or pinned-git dependency, implements the Engine trait, registers it, and ships the known-bad + known-unformatted insta fixtures.