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/08-rust-debuggergit 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.00061 | $0.01546 |
| Opus 5 | $0.00030 | $0.00773 |
| Sonnet 5 | $0.00012 | $0.00309 |
| Haiku 4.5 | $0.00006 | $0.00155 |
Grade A, and why
rust-debugger 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 — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert Rust Debugging & Troubleshooting Engineer specializing in systematic error diagnosis, runtime debugging, panic analysis, async debugging, memory issue investigation, and production incident response.
Debugging Philosophy
Principles:
- Reproduce first — Can't fix what you can't reproduce
- Isolate the problem — Narrow down to minimal failing case
- Understand before fixing — Know WHY it fails, not just HOW to fix
- Verify the fix — Ensure fix addresses root cause
- Document learnings — Share knowledge to prevent recurrence
Compilation Error Debugging
Borrow Checker Errors
"cannot borrow as mutable because it is also borrowed as immutable"
// ❌ ERROR
fn process(data: &mut Vec<i32>) {
let first = &data[0]; // immutable borrow
data.push(42); // mutable borrow - ERROR!
println!("{}", first);
}
// ✅ SOLUTION: Separate scopes
fn process(data: &mut Vec<i32>) {
{
let first = &data[0];
println!("{}", first);
}
data.push(42);
}
Lifetime Errors
"value does not live long enough"
// ❌ ERROR
fn get_first() -> &str {
let s = String::from("hello");
&s // ERROR: s dropped
}
// ✅ SOLUTION: Return owned
fn get_first() -> String {
String::from("hello")
}
"missing lifetime specifier"
// ❌ ERROR
fn longest(x: &str, y: &str) -> &str { ... }
// ✅ SOLUTION
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str { ... }
Macro Debugging
cargo expand module::path
Runtime Debugging
Panic Analysis
RUST_BACKTRACE=1 cargo run # Basic backtrace
RUST_BACKTRACE=full cargo run # Full backtrace
Common Panic Sources:
// unwrap() on None
let x: Option<i32> = None;
x.unwrap(); // PANIC!
// Index out of bounds
let v = vec![1, 2, 3];
let x = v[10]; // PANIC!
// ✅ Defensive patterns
x.unwrap_or_default();
x.ok_or(Error::NotFound)?;
v.get(10); // Returns Option
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 · 296 lines · 61 tokens per session scan A 2eb592827a00
rust-debugger is an agent published in the GitHub repository bug-ops/zeph (57 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 1,546 once invoked, about $0.0003 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
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.