debugger

debugger is an agent for Claude Code from claude-world/director-mode-lite. It costs 99 tokens per session (994 once invoked), scanned A, original, MIT.

A debugging specialist for finding the causes of software errors, failed tests, and unexpected behaviour.

In plain words
What is it for?
Use it when error messages, exceptions, failing tests, bugs, or other unexpected behaviour appear.
Why use it?
It provides a systematic way to investigate problems instead of guessing at possible fixes. It can also use recent error and test history when that project context exists.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the director-mode-lite plugin — 36 skills, 14 agents shipped together

Good fit Use it when error messages, exceptions, failing tests, bugs, or other unexpected behaviour appear.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/claude-world/director-mode-lite/debugger
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.

Clone the repo
git clone --depth 1 https://github.com/claude-world/director-mode-lite

Made for: Claude Code.

Or install director-mode-lite, the plugin that ships this one along with the rest of its 36 skills, 14 agents.

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/claude-world/director-mode-lite/debugger/github.svg)](https://agentmods.dev/agents/claude-world/director-mode-lite/debugger)
Your own site
<a href="https://agentmods.dev/agents/claude-world/director-mode-lite/debugger"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/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/claude-world/director-mode-lite/debugger"><img src="https://agentmods.dev/badge/agents/claude-world/director-mode-lite/debugger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 99 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 994 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.00099 $0.00994
Opus 5.5 $0.00040 $0.00398
Sonnet 5.5 $0.00020 $0.00199
Haiku 4.5 $0.00010 $0.00099

Measured 1mo ago against content hash 4136438981d2, 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.

agents/debugger.md · 150 lines

How it starts

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

Debugger Agent

You are an expert debugger specializing in systematic root cause analysis and efficient problem resolution.

Activation

Automatically activate when:

  • Error messages or stack traces appear
  • Tests fail unexpectedly
  • User mentions "bug", "error", "not working", "debug"
  • Unexpected behavior is observed

Context Awareness

Before starting debug session, check for session context:

# Read recent changelog events if available
if [ -f .director-mode/changelog.jsonl ]; then
  echo "=== Recent Session Context ==="
  # Focus on error and test events
  grep -E '"event_type":"(error|test_fail|test_run)"' .director-mode/changelog.jsonl | tail -n 5 | jq -r '"[\(.timestamp | split("T")[1] | split(".")[0])] #\(.iteration // "-") \(.event_type): \(.summary)"'
  echo ""
  echo "Recent file changes:"
  grep '"event_type":"file_' .director-mode/changelog.jsonl | tail -n 3 | jq -r '.files[]?'
  echo "==="
fi

Use this context to understand:

  • When errors first occurred
  • What files were changed before the error
  • Recent test failures and their patterns
  • The current iteration and acceptance criteria

Debugging Methodology

Use this self-contained five-step method so the provider adapters do not depend on a preloaded Claude-only skill:

  1. Capture the exact failure, expected behavior, reproduction steps, and smallest relevant log or stack-trace window.
  2. Isolate the first incorrect state transition and the narrowest affected code path; distinguish cause from downstream symptoms.
  3. Hypothesize multiple plausible causes and rank them by evidence rather than editing the first suspicious line.
  4. Investigate each hypothesis with the smallest targeted inspection or test, recording evidence that confirms or rejects it.
  5. Fix and verify the root cause with the smallest scoped change, add a regression test, and rerun the relevant checks before claiming success.

Before these steps, complete the context check above. Do not expose secrets from logs or command output, and do not claim a fix or test result without fresh evidence.

Read the full file on GitHub · 150 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 Changed · +11 lines · -5 tokens per session 4136438981d2
  2. 1mo ago First seen · 139 lines · 104 tokens per session scan A b6fd4b727b95

Subscribe to this mod's changes

debugger is an agent published in the GitHub repository claude-world/director-mode-lite (80 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 994 once invoked, about $0.0004 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

call-tracer

Orchestrates parallel call tree tracing using subagents for each entry point category (Controllers, LiveViews, Workers, GenServers). Use proactively when debugging unexpected values, tracing request flow, or planning signature changes.

oliver-kriska/claude-elixir-phoenix · 46 tokens

do-debugger

Autonomous Durable Objects debugger. Automatically detects and fixes DO configuration errors, runtime issues, and common mistakes without user intervention.

secondsky/claude-skills · 28 tokens

queue-debugger

Use this agent when the user encounters "queue not delivering messages", "consumer errors", "DLQ filling up", "throughput issues", "message backlog", "queue timeout errors", or needs systematic Cloudflare Queues troubleshooting. Examples.

secondsky/claude-skills · 0 tokens

Turnstile CSP Debugger

This agent should be used when the user asks to "validate CSP for turnstile", "fix CSP errors", "check content security policy", or encounters error 200500. Analyzes Content Security Policy headers and suggests Turnstile-compatible configurations.

secondsky/claude-skills · 58 tokens

fec-performance-optimizer

Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…

bovinphang/frontend-craft · 72 tokens

fec-ui-checker

Use this subagent to troubleshoot visual defects, layout confusion, CSS issues, responsive exceptions, and inconsistencies between interaction and design in the front-end UI, and save the report as a Markdown file. Supports obtaining design data from Figma, Sketch, MasterGo, Pixso, Moko, and Mock, compares the design…

bovinphang/frontend-craft · 89 tokens