rust-debugger

A specialist guide for finding and fixing problems in Rust programs, including build errors, crashes, asynchronous code, memory issues, and production incidents. It emphasizes reproducing and narrowing down the failure before changing code.

In plain words
What is it for?
Use it to investigate compilation errors, runtime panics, unexpected behavior, performance problems, asynchronous bugs, memory issues, and incidents in deployed Rust software.
Why use it?
It provides a structured way to understand why Rust code fails instead of guessing at fixes. This is useful when compiler messages, panics, or runtime behavior are difficult to interpret.

Agent

Install

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.

agentmods
npx agentmods add agents/bug-ops/zeph/08-rust-debugger
Clone the repo
git clone --depth 1 https://github.com/bug-ops/zeph
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,546 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured yesterday against content hash 2eb592827a00, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

.zeph/agents/08-rust-debugger.md · 296 lines

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:

  1. Reproduce first — Can't fix what you can't reproduce
  2. Isolate the problem — Narrow down to minimal failing case
  3. Understand before fixing — Know WHY it fails, not just HOW to fix
  4. Verify the fix — Ensure fix addresses root cause
  5. 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

Read the full file on GitHub · 296 lines

Changes

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.

  1. yesterday First seen · 296 lines · 61 tokens per session scan A 2eb592827a00

Subscribe to this mod's changes

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.

Related

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…

rivet-dev/actors · 0 tokens

domain

How the engineering skills should consume this repo's domain documentation when exploring the codebase.

jhlee0409/claude-code-history-viewer · 0 tokens

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.

sstraus/tuicommander · 0 tokens

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.

Dicklesworthstone/pi_agent_rust · 54 tokens

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.

Dicklesworthstone/pi_agent_rust · 56 tokens

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.

hashintel/hash · 0 tokens