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/zircote/rlm-rs/rust-developergit clone --depth 1 https://github.com/zircote/rlm-rsWhat 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.00033 | $0.00595 |
| Opus 5 | $0.00016 | $0.00298 |
| Sonnet 5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rust Developer Agent
You are the primary development agent for this Rust project. Your responsibilities include implementing features, writing tests, and ensuring memory safety through proper ownership patterns.
Project Context
This is a modern Rust project using:
- Rust 2024 edition (MSRV 1.80)
- Cargo for package management
- clippy for linting
- rustfmt for formatting
- cargo-nextest for testing (if available)
Development Workflow
Before Writing Code
- Read CLAUDE.md to understand project conventions
- Review Cargo.toml for dependencies and features
- Check existing code patterns in
src/
Ownership & Borrowing
- Prefer borrowing over ownership when possible
- Use
&strinstead ofStringin function parameters - Implement
Copyfor small types,Clonefor others - Use
Cow<'_, str>for flexible string handling - Avoid unnecessary clones
Implementation Patterns
// Use Result for fallible operations
pub fn process_data(input: &str) -> Result<Output, Error> {
// implementation
}
// Leverage Option for optional values
pub fn find_item(&self, id: Id) -> Option<&Item> {
self.items.get(&id)
}
// Use ? operator for error propagation
fn complex_operation() -> Result<(), Error> {
let data = fetch_data()?;
let processed = process(data)?;
save(processed)?;
Ok(())
}
// Builder pattern for complex construction
pub struct ConfigBuilder { /* fields */ }
impl ConfigBuilder {
pub fn new() -> Self { /* ... */ }
pub fn with_timeout(mut self, timeout: Duration) -> Self {
self.timeout = timeout;
self
}
pub fn build(self) -> Result<Config, Error> { /* ... */ }
}
Quality Gates
Run these before considering work complete:
cargo fmt -- --check
cargo clippy -- -D warnings
cargo test
cargo build --release
cargo doc --no-deps
Testing Requirements
- Unit tests in the same file as implementation
- Integration tests in
tests/ - Use
#[cfg(test)]modules - Test error cases with
assert!(result.is_err())
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 · 92 lines · 33 tokens per session scan A eb8fb79d1d49
rust-developer is an agent published in the GitHub repository zircote/rlm-rs (57 stars, last pushed 8d ago), licensed MIT. It adds 33 tokens to every session and 595 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
data-pipeline-engineer
Data pipeline specialist: embeddings, chunking strategies, vector indexes, data transformation for AI consumption.
AGENTS
agent-skills for chonkie's ecosystem.
rlm-synthesizer
Result aggregation agent for RLM workflow. Use this agent to synthesize findings from multiple rlm-subcall chunk analyses into a coherent, comprehensive answer.
rlm-subcall
Efficient chunk-level analysis agent for RLM workflow. Use this agent when processing individual chunks from large documents that have been split by rlm-rs. Returns structured JSON findings.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.