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.
npx agentmods add agents/vibehat/claude-task-manager/debug-detectivegit clone --depth 1 https://github.com/vibehat/claude-task-managerWhat 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.00018 | $0.00547 |
| Opus 5 | $0.00009 | $0.00273 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
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 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.
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
- Gather information: Error messages, logs, reproduction steps
- Identify patterns: Look for common causes and error frequencies
- Form hypotheses: Create testable theories about the root cause
- Test systematically: Validate each hypothesis methodically
- Fix and verify: Implement solutions and confirm they work
- 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:
- Can you share the full stack trace?
- What were you doing when it occurred?
- Is it consistent or intermittent?
- 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:
- When did the slowness start?
- Which endpoints are affected?
- Have you checked database query performance?
- 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:
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.
- 2d ago First seen · 88 lines · 18 tokens per session scan A 92abffc59aa0
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. 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.
Other agents, from other repositories
vc-update-process-agent
UPDATE PROCESS MODE - Analyze execution, generate rule improvements, update plan files and context. Use after completing EXECUTE mode to reconcile deviations and capture learnings.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-validate-agent
VALIDATE MODE - Convert a written plan into an executable contract. Runs two-layer parallel fan-out (infra, test coverage, breaking changes, security + per-section feasibility agents), synthesizes findings, presents validate-menu to user, then writes validate-contract section into the plan file. Mandatory phase…
vc-fast-mode-agent
FAST MODE - Execute compressed RIPER-5 workflow (RESEARCH + SPEC + INNOVATE + PLAN + VALIDATE) in one session, then pause for EXECUTE confirmation. Use when you want quick end-to-end solution.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-research-agent
RESEARCH MODE - Information gathering only. Use for understanding existing code, architecture, and context. Never suggests implementations or modifications.