claude-task-manager: Agent for Claude Code

.claude/agents/debug-detective.md

Debug Detective is an agent for Claude Code from vibehat/claude-task-manager. It costs 18 tokens per session (547 once invoked), scanned A, original, MIT.

An agent role focused on finding and fixing software bugs by studying symptoms, logs, stack traces, performance problems, memory leaks, race conditions, and integration failures.

In plain words
What is it for?
Use it to investigate errors, narrow down causes, interpret logs, diagnose bottlenecks or leaks, and add tests or monitoring after a fix.
Why use it?
It provides a systematic path from reproduction and hypothesis testing to verified fixes and measures that prevent the bug returning.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is vibehat/claude-task-manager's own configuration. It tells Claude Code how to work on claude-task-manager 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 claude-task-manager configures →

Reuse

Borrowing it

Nothing to install: this file belongs to vibehat/claude-task-manager. 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/vibehat/claude-task-manager/master/.claude/agents/debug-detective.md
Clone the repo
git clone --depth 1 https://github.com/vibehat/claude-task-manager

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 Debug Detective

README.md
[![agentmods](https://agentmods.dev/badge/agents/vibehat/claude-task-manager/debug-detective/github.svg)](https://agentmods.dev/agents/vibehat/claude-task-manager/debug-detective)
Your own site
<a href="https://agentmods.dev/agents/vibehat/claude-task-manager/debug-detective"><img src="https://agentmods.dev/badge/agents/vibehat/claude-task-manager/debug-detective/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 Debug Detective

Your own site · 80×15
<a href="https://agentmods.dev/agents/vibehat/claude-task-manager/debug-detective"><img src="https://agentmods.dev/badge/agents/vibehat/claude-task-manager/debug-detective.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 547 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.00018 $0.00547
Opus 5.5 $0.00007 $0.00219
Sonnet 5.5 $0.00004 $0.00109
Haiku 4.5 $0.00002 $0.00055

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

Security

Grade A, and why

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

.claude/agents/debug-detective.md · 88 lines

How it starts

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

Debug Detective

Purpose

I specialize in hunting down bugs, analyzing error patterns, and helping you troubleshoot complex issues. I approach debugging systematically and help you understand root causes.

Guidelines

  • Start with symptoms: Document the exact behavior and error messages
  • Reproduce consistently: Help establish reliable reproduction steps
  • Narrow the scope: Use binary search and isolation techniques
  • Check the obvious: Validate assumptions and common pitfalls first
  • Document solutions: Create clear explanations for future reference

Core Capabilities

  • Error log analysis and pattern recognition
  • Stack trace interpretation
  • Performance bottleneck identification
  • Memory leak detection
  • Race condition analysis
  • Integration failure diagnosis

Debugging Process

  1. Gather information: Error messages, logs, reproduction steps
  2. Identify patterns: Look for common causes and error frequencies
  3. Form hypotheses: Create testable theories about the root cause
  4. Test systematically: Validate each hypothesis methodically
  5. Fix and verify: Implement solutions and confirm they work
  6. Prevent recurrence: Add tests or monitoring to catch similar issues

Examples

Runtime Error

"I'm getting a NullPointerException in my Java app"

Let's debug this step by step:

  1. Can you share the full stack trace?
  2. What were you doing when it occurred?
  3. Is it consistent or intermittent?
  4. Are there any recent code changes?

I'll help you trace the null reference and implement proper null safety.

Performance Issue

"My API responses are suddenly very slow"

I'll help you investigate:

  1. When did the slowness start?
  2. Which endpoints are affected?
  3. Have you checked database query performance?
  4. Are there any new deployments or data volume changes?

We'll use profiling tools to identify the bottleneck.

Integration Problem

"External API calls are failing randomly"

Let's troubleshoot the integration:

Read the full file on GitHub · 88 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 · 88 lines · 18 tokens per session scan A 92abffc59aa0

Subscribe to this mod's changes

Debug Detective is an agent published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It adds 18 tokens to every session and 547 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

qa-analyzer

Use this agent after cycle completion or when the user requests bug hunting and QA analysis. World-class QA analyst that finds bugs before users do — thinks like a confused user, power user, and malicious attacker. Documents each issue precisely so it can be filed as a bug. Context: User just completed a cycle and…

drobins25/craft · 223 tokens

mb-debugger

Systematic-debugging specialist for memory-bank. Use when a bug, failing test, flaky test, crash, regression, or unexpected behaviour must be explained and fixed — finds the root cause with evidence before any fix, then lands a failing test, a single fix, and verification output.

fockus/skill-memory-bank · 61 tokens

bulwark-fix-validator

Validates fixes against debug report by executing tiered test plan and assessing confidence. Reads validation plan from IssueAnalyzer output. Use proactively after a fix has been implemented and a debug report exists, to validate the fix and assess deployment confidence.

QBall-Inc/the-bulwark · 54 tokens

bulwark-implementer

Code-writing agent that implements fixes and features following Bulwark standards. Quality enforced by direct implementer-quality.sh invocation after each Write/Edit. Use proactively after a debug report (fix mode) or design document (feature mode) is ready for implementation.

QBall-Inc/the-bulwark · 57 tokens

bulwark-issue-analyzer

Analyzes issues to identify root cause, map impact, and produce debug report with tiered validation plan. Supports both production code bugs and test code issues.

QBall-Inc/the-bulwark · 39 tokens

debugger

Systematic debugging using scientific method. Persistent debug sessions with hypothesis testing, evidence tracking, and checkpoint support.

SienkLogic/plan-build-run · 24 tokens