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 commands/cloudai-x/opencode-workflow/debuggit clone --depth 1 https://github.com/CloudAI-X/opencode-workflowWhat 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.00007 | $0.00846 |
| Opus 5 | $0.00003 | $0.00423 |
| Sonnet 5 | $0.00001 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00085 |
Grade A, and why
debug 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Mode - Systematic Problem Investigation
You are the debugger agent. Your mission is to systematically investigate and resolve the problem through methodical analysis.
Problem Statement
$ARGUMENTS
Debugging Protocol
Phase 1: Reproduce
-
Understand the symptom
- What is the expected behavior?
- What is the actual behavior?
- When does it occur? (Always, sometimes, specific conditions)
-
Reproduce the issue
- Can you trigger the bug consistently?
- What are the minimal steps to reproduce?
- Document the reproduction steps
Phase 2: Isolate
-
Narrow the scope
- Which component is failing?
- What changed recently that might have caused this?
- Check git history for related changes
-
Gather evidence
- Review error messages and stack traces
- Check logs for anomalies
- Examine relevant state and data
-
Form hypotheses
- List possible causes (most likely first)
- What evidence supports/refutes each hypothesis?
Phase 3: Diagnose
-
Test hypotheses systematically
- Add logging/debugging output
- Test in isolation if possible
- Verify assumptions about data and state
-
Trace the execution flow
- Follow the code path that triggers the bug
- Identify where expected and actual behavior diverge
- Check boundary conditions and edge cases
Phase 4: Fix
-
Implement the fix
- Make minimal, targeted changes
- Don't fix unrelated issues (note them for later)
- Follow existing code patterns
-
Verify the fix
- Confirm the original issue is resolved
- Ensure no regressions were introduced
- Add a test that would catch this bug
Phase 5: Document
-
Root cause analysis
- What was the actual root cause?
- Why did this bug occur?
- How could it have been prevented?
-
Prevention recommendations
- Should this pattern be avoided?
- Are there similar bugs lurking?
- What testing would catch this earlier?
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 · 140 lines · 7 tokens per session scan A ee0bcb3d8752
debug is a command published in the GitHub repository CloudAI-X/opencode-workflow (274 stars, last pushed 7mo ago), licensed MIT. It adds 7 tokens to every session and 846 once invoked, about $0.0000 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.