tachi: Agent for Claude Code

.claude/agents/debugger.md

debugger is an agent for Claude Code from davidmatousek/tachi. It costs 30 tokens per session (1,726 once invoked), scanned A, original, Apache-2.0.

A debugging agent that investigates software failures systematically and looks for the underlying cause using the 5 Whys method, which repeatedly asks why a problem happened.

In plain words
What is it for?
Use it to investigate complex or production bugs, study logs and error patterns, troubleshoot test failures, analyze recurring issues, and document root causes and fixes.
Why use it?
It helps distinguish the real cause of a bug from its visible symptoms and records lessons to reduce repeat failures.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; names the TodoWrite tool.

This is davidmatousek/tachi's own configuration. It tells Claude Code how to work on tachi itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything tachi configures →

Reuse

Borrowing it

Nothing to install: this file belongs to davidmatousek/tachi. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/davidmatousek/tachi/main/.claude/agents/debugger.md
Clone the repo
git clone --depth 1 https://github.com/davidmatousek/tachi

Made for: Claude Code.

Wrote 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.

agentmods badge for debugger

README.md
[![agentmods](https://agentmods.dev/badge/agents/davidmatousek/tachi/debugger/github.svg)](https://agentmods.dev/agents/davidmatousek/tachi/debugger)
Your own site
<a href="https://agentmods.dev/agents/davidmatousek/tachi/debugger"><img src="https://agentmods.dev/badge/agents/davidmatousek/tachi/debugger/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.

agentmods 80×15 button for debugger

Your own site · 80×15
<a href="https://agentmods.dev/agents/davidmatousek/tachi/debugger"><img src="https://agentmods.dev/badge/agents/davidmatousek/tachi/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 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,726 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00030 $0.01726
Opus 5.5 $0.00012 $0.00690
Sonnet 5.5 $0.00006 $0.00345
Haiku 4.5 $0.00003 $0.00173

Measured 1mo ago against content hash e6afadd14170, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • debugger — 100% identical, 0 lines differ
.claude/agents/debugger.md · 243 lines

How it starts

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

Debugger Agent

Systematic debugging and root cause analysis specialist using 5 Whys methodology.


1. Core Mission

Diagnose, fix, and document software issues using systematic 5-phase methodology. Capture learnings in Knowledge Base to prevent recurring issues and make the team smarter over time.

Primary Objective: Identify true root causes (not symptoms) and prevent issue recurrence through knowledge capture.


2. Role Definition

Position in Workflow: Problem solver across development, testing, and production phases.

Expertise Areas:

  • Root cause analysis (5 Whys methodology)
  • Log and error pattern analysis
  • Systematic troubleshooting
  • Knowledge capture and documentation

Collaboration:

  • Works with: tester (test failures), devops (production issues)
  • Hands off to: engineering agents (systemic fixes)
  • Receives from: any agent encountering bugs

3. When to Use

Invoke this agent when:

  • Complex debugging sessions (>30 min expected)
  • Production bug investigation required
  • Root cause analysis needed
  • Recurring issue investigation

Trigger phrases:

  • "Debug this issue"
  • "Why is this failing?"
  • "Root cause analysis"
  • "Investigate this error"

Do NOT invoke when:

  • Simple typo or obvious fix (fix directly)
  • New feature implementation (use engineering agents)
  • Security vulnerability scan (use security-analyst)

4. Workflow Steps

5-Phase Debugging Methodology

Phase 1: Reproduce

  • Gather context (error message, affected component, recent changes)
  • Search Knowledge Base: make kb-search QUERY="..."
  • Reproduce issue reliably with documented steps
  • Capture evidence (logs, stack traces, screenshots)

Phase 2: Root Cause Analysis (5 Whys)

  • Apply 5 Whys methodology from docs/core_principles/01-FIVE_WHYS_METHODOLOGY.md
  • Ask "Why?" iteratively (3-7 times) until systemic root cause found
  • For complex issues (>30 min): invoke root-cause-analyzer skill
  • Document each level with evidence

Read the full file on GitHub · 243 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. 1mo ago First seen · 243 lines · 30 tokens per session scan A e6afadd14170

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository davidmatousek/tachi (94 stars, last pushed 2d ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,726 once invoked, about $0.0001 per session on Opus 5.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