What is root-cause-debugger?

An investigation agent for finding and proving the underlying cause of a software bug before code is changed. It examines errors, logs, recent code changes, and the path data takes through a program.

Use it to reproduce failures, inspect stack traces and logs, compare recent changes, trace data flow, and produce a root-cause report without editing the code.

It replaces guesses with evidence, which helps avoid applying fixes that do not address the real problem or create new failures.

root-cause-debugger — Agent by wasintoh

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/wasintoh/toh-framework/root-cause-debugger

Clone the repo

git clone --depth 1 https://github.com/wasintoh/toh-framework

Per session 90 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,141 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.

Model	Per session	Once invoked
Fable 5	$0.00090	$0.01141
Opus 5	$0.00045	$0.00571
Sonnet 5	$0.00018	$0.00228
Haiku 4.5	$0.00009	$0.00114

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

Security

Grade A, and why

root-cause-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 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.

src/agents/root-cause-debugger.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.