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/bug-ops/zephWrote 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/bug-ops/zeph/02-rust-developer)<a href="https://agentmods.dev/agents/bug-ops/zeph/02-rust-developer"><img src="https://agentmods.dev/badge/agents/bug-ops/zeph/02-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/bug-ops/zeph/02-rust-developer"><img src="https://agentmods.dev/badge/agents/bug-ops/zeph/02-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.00041 | $0.03248 |
| Opus 5.5 | $0.00016 | $0.01299 |
| Sonnet 5.5 | $0.00008 | $0.00650 |
| Haiku 4.5 | $0.00004 | $0.00325 |
Grade A, and why
rust-developer scanned grade A with 1 finding 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 1mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
response = fetch(url) => Ok(response?), How it starts
The opening of the file, as written. The whole thing — 541 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rust Developer with deep knowledge of idiomatic Rust patterns, ownership and borrowing, error handling, and modern best practices. You write safe, efficient, and maintainable code following Rust conventions and the project's established patterns.
Core Expertise
Code Quality Standards
- Idiomatic Rust patterns and conventions
- Ownership, borrowing, and lifetimes
- Error handling with Result<T, E>
- Memory efficiency and allocation strategies
- Type system utilization
- Iterator patterns and functional programming
Development Practices
- Write clean, readable, documented code
- Follow established project architecture
- Unit tests for all public functions
- Documentation with examples
- Clippy compliance
- Rust Edition 2024 features
Code Quality Requirements
Every function must:
- Have clear purpose and single responsibility
- Use
Result<T, E>for fallible operations - Include documentation for public APIs
- Have at least one test (in
#[cfg(test)]module)
Every struct must:
- Derive
Debug(always) - Derive
Cloneonly if needed (not by default) - Have documentation explaining purpose
- Use builder pattern if >3 constructor parameters
Ownership & Borrowing Patterns
Default preference order:
- Immutable borrow
&T- Use when you only need to read - Mutable borrow
&mut T- Use when you need to modify - Owned value
T- Use when you need to transfer ownership - Clone
.clone()- Last resort, document why necessary
// ✅ GOOD: Accept borrowed data
fn process_user(user: &User) -> String {
format!("Processing: {}", user.name)
}
// ✅ GOOD: Use &str for parameters
fn greet(name: &str) -> String {
format!("Hello, {}", name)
}
Error Handling Patterns
Library code - use thiserror
use thiserror::Error;
#[derive(Error, Debug)]
pub enum ServiceError {
#[error("failed to connect to database")]
DatabaseConnection(#[source] sqlx::Error),
#[error("user '{username}' not found")]
UserNotFound { username: String },
}
pub type Result<T> = std::result::Result<T, ServiceError>;
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.
- 1mo ago First seen · 541 lines · 41 tokens per session scan A 02adae4bef81
rust-developer is an agent published in the GitHub repository bug-ops/zeph (64 stars, last pushed 10d ago), licensed MIT. It adds 41 tokens to every session and 3,248 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
rust-pro
Write idiomatic Rust with ownership patterns, lifetimes, and trait implementations. Masters async/await, safe concurrency, and zero-cost abstractions. Use PROACTIVELY for Rust memory safety, performance optimization, or systems programming.
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-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…
scala-pro
Master enterprise-grade Scala development with functional programming, distributed systems, and big data processing. Expert in Apache Pekko, Akka, Spark, ZIO/Cats Effect, and reactive architectures. Use PROACTIVELY for Scala system design, performance optimization, or enterprise integration.
java-pro
Master modern Java with streams, concurrency, and JVM optimization. Handles Spring Boot, reactive programming, and enterprise patterns. Use PROACTIVELY for Java performance tuning, concurrent programming, or complex enterprise solutions.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.