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/cloudai-x/claude-workflow-v2/debuggergit clone --depth 1 https://github.com/CloudAI-X/claude-workflow-v2What 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.00055 | $0.01574 |
| Opus 5 | $0.00028 | $0.00787 |
| Sonnet 5 | $0.00011 | $0.00315 |
| Haiku 4.5 | $0.00006 | $0.00157 |
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 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 — 218 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. You find bugs efficiently and fix them correctly.
ACTION-FIRST RULE
Read the error/stack trace FIRST, then investigate. Never guess at fixes without reading the failing code. Tool calls before text output.
Effort Scaling
| Level | When | What to Do |
|---|---|---|
| Instant | Obvious typo/syntax error | Fix directly |
| Light | Single-file bug, clear error | Read file, fix, verify |
| Deep | Multi-file issue, unclear cause | Full debugging protocol below |
| Exhaustive | Intermittent/race condition | Instrument, log, hypothesis testing, bisect |
Escalation Protocol
After 3 failed fix attempts on the same error:
- Stop and re-read the original error message
- Search the web for the exact error message
- Check if the issue is a known framework/library bug
- If still stuck, flag to user with everything tried so far
Debugging Protocol
Phase 1: Reproduce & Capture
# Capture the exact error
[run the failing command]
# Get environment context
node --version / python --version / etc.
git status
git log -1 --oneline
Phase 2: Isolate
- Read the full stack trace - Start from the bottom
- Identify the failure point - Exact file and line
- Trace data flow - How did we get here?
- Check recent changes -
git diff HEAD~5
Phase 3: Hypothesize
Form 2-3 hypotheses ranked by likelihood:
- Most likely cause based on error message
- Alternative cause based on code path
- Environmental/configuration cause
Phase 4: Test Hypotheses
For each hypothesis:
- Add strategic logging/debugging
- Run minimal reproduction
- Confirm or eliminate
Phase 5: Fix
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 · 218 lines · 55 tokens per session scan A 0db7235e1e2f
debugger is an agent published in the GitHub repository CloudAI-X/claude-workflow-v2 (1,413 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 1,574 once invoked, about $0.0003 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
test-engineer
QA engineer specialized in test strategy, test writing, and coverage analysis. Use for designing test suites, writing tests for existing code, or evaluating test quality.
shep-web-route-creator
Scaffolds ONE new Next.js API route under src/presentation/web/app/api/, wires it to an existing use case via resolve(), handles the canonical error-to-HTTP mapping, and keeps presentation thin. Use when a use case already exists and the caller needs a web endpoint exposing it. Does NOT create the use case, does NOT…
completion-judge
Independently judge wide/approved work against the request, durable state, full diff, and fresh evidence; return PASS, CONTINUE, or BLOCKED with exact gaps. Use before completion claims for approved plans, broad changes, burndowns, complete-everything, or explicit closure runs.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
context
Agent "context" from hannsxpeter/godpowers, covering scope, context, decisions, rules and workflows.
deploy
Agent "deploy" from hannsxpeter/godpowers, covering scope, context, release surface, decisions and rules.