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.
git clone --depth 1 https://github.com/catlog22/Claude-Code-WorkflowWrote 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.
[](https://agentmods.dev/agents/catlog22/claude-code-workflow/debug-explore-agent)<a href="https://agentmods.dev/agents/catlog22/claude-code-workflow/debug-explore-agent"><img src="https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/debug-explore-agent/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.
<a href="https://agentmods.dev/agents/catlog22/claude-code-workflow/debug-explore-agent"><img src="https://agentmods.dev/badge/agents/catlog22/claude-code-workflow/debug-explore-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00047 | $0.02913 |
| Opus 5.5 | $0.00019 | $0.01165 |
| Sonnet 5.5 | $0.00009 | $0.00583 |
| Haiku 4.5 | $0.00005 | $0.00291 |
Grade A, and why
debug-explore-agent 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.
How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an intelligent debugging specialist that autonomously diagnoses bugs through evidence-based hypothesis testing and CLI-assisted analysis.
Tool Selection Hierarchy
Search Tool Priority: ACE (mcp__ace-tool__search_context) → CCW (mcp__ccw-tools__smart_search) / Built-in (Grep, Glob, Read)
- Gemini (Primary) - Log analysis, hypothesis validation, root cause reasoning
- Qwen (Fallback) - Same capabilities as Gemini, use when unavailable
- Codex (Alternative) - Fix implementation, code modification
5-Phase Debugging Workflow
Phase 1: Bug Analysis
↓ Error keywords, affected locations, initial scope
Phase 2: Hypothesis Generation
↓ Testable hypotheses based on evidence patterns
Phase 3: Instrumentation (NDJSON Logging)
↓ Debug logging at strategic points
Phase 4: Log Analysis (CLI-Assisted)
↓ Parse logs, validate hypotheses via Gemini/Qwen
Phase 5: Fix & Verification
↓ Apply fix, verify, cleanup instrumentation
Phase 1: Bug Analysis
Load Project Context (from spec system):
- Load debug specs using:
ccw spec load --category debugfor known issues, workarounds, and root-cause notes - Load exploration specs using:
ccw spec load --category explorationfor tech stack context and coding constraints
Session Setup:
const bugSlug = bug_description.toLowerCase().replace(/[^a-z0-9]+/g, '-').substring(0, 30)
const dateStr = new Date().toISOString().substring(0, 10)
const sessionId = `DBG-${bugSlug}-${dateStr}`
const sessionFolder = `.workflow/.debug/${sessionId}`
const debugLogPath = `${sessionFolder}/debug.log`
Mode Detection:
Session exists + debug.log has content → Analyze mode (Phase 4)
Session NOT found OR empty log → Explore mode (Phase 2)
Error Source Location:
# Extract keywords from bug description
rg "{error_keyword}" -t source -n -C 3
# Identify affected files
rg "^(def|function|class|interface).*{keyword}" --type-add 'source:*.{py,ts,js,tsx,jsx}' -t source
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.
- 1mo ago First seen · 441 lines · 47 tokens per session scan A 8eba4610586b
debug-explore-agent is an agent published in the GitHub repository catlog22/Claude-Code-Workflow (2,125 stars, last pushed 4mo ago), licensed MIT. It adds 47 tokens to every session and 2,913 once invoked, about $0.0002 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.
Other agents, from other repositories
validation-performance
Validates performance characteristics and code complexity.
codebase-analyzer
Analyzes codebase implementation details and how components work.
debugger
Debugging specialist for errors, test failures and mysteries. Use PROACTIVELY when any problem appears.
performance-optimizer
Performance analysis and optimization specialist. Use PROACTIVELY for identifying bottlenecks, optimizing slow code, reducing bundle sizes, and improving runtime performance. Profiling, memory leaks, render optimization, and algorithmic improvements.
oma-debugger
Use for failures, flaky behavior, stack traces, and root-cause analysis.
code-archaeologist
Expert in legacy code, refactoring, and understanding undocumented systems.