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/bug-ops/zeph/02-rust-developergit clone --depth 1 https://github.com/bug-ops/zephWhat 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.00041 | $0.03248 |
| Opus 5 | $0.00020 | $0.01624 |
| Sonnet 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 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.
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.
- yesterday First seen · 541 lines · 41 tokens per session scan A 02adae4bef81
rust-developer is an agent published in the GitHub repository bug-ops/zeph (57 stars, last pushed 7d ago), licensed MIT. It adds 41 tokens to every session and 3,248 once invoked, about $0.0002 per session on Opus 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
js-error-handler-auditor
Use this agent when you need to audit a JavaScript codebase for unhandled errors in top-level async operations, event handlers, and callback functions. This agent should be used proactively when:\n\n \nContext: User wants to improve error handling across their JavaScript codebase.\nuser: "Can you check if we're…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
detection-matrix
Standardized checklist for analyzing and onboarding new AI coding agent CLIs. Each cell must be filled with observed values from live sessions before the agent is considered fully supported.
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
temporal-python-pro
Master Temporal workflow orchestration with Python SDK. Implements durable workflows, saga patterns, and distributed transactions. Covers async/await, testing strategies, and production deployment. Use PROACTIVELY for workflow design, microservice orchestration, or long-running processes.
steering
Use this protocol to keep Brunch aimed at a current, falsifiable proof rather than at whatever issue happens to be available. The arc driver owns trigger evaluation. Current truth lives in STEERING, which references governing STRATEGY-LOG IDs; this document owns only the control loop.