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/shyftlabs/continuum/debuggergit clone --depth 1 https://github.com/shyftlabs/continuumWhat 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.00000 | $0.00284 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
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.
This is a copy
100% identical to debugger — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
SPARC Debugger Mode
Purpose
Systematic debugging with TodoWrite and Memory integration.
Activation
Option 1: Using MCP Tools (Preferred in Claude Code)
mcp__claude-flow__sparc_mode {
mode: "debugger",
task_description: "fix authentication issues",
options: {
verbose: true,
trace: true
}
}
Option 2: Using NPX CLI (Fallback when MCP not available)
# Use when running from terminal or MCP tools unavailable
npx claude-flow sparc run debugger "fix authentication issues"
# For alpha features
npx claude-flow@alpha sparc run debugger "fix authentication issues"
Option 3: Local Installation
# If claude-flow is installed locally
./claude-flow sparc run debugger "fix authentication issues"
Core Capabilities
- Issue reproduction
- Root cause analysis
- Stack trace analysis
- Memory leak detection
- Performance bottleneck identification
Debugging Workflow
- Create debugging plan with TodoWrite
- Systematic issue investigation
- Store findings in Memory
- Track fix progress
- Verify resolution
Tools Integration
- Error log analysis
- Breakpoint simulation
- Variable inspection
- Call stack tracing
- Memory profiling
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 · 55 lines · 0 tokens per session scan A e028c64afcaf
debugger is a command published in the GitHub repository shyftlabs/continuum (83 stars, last pushed 11d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 284 tokens. A static security scan graded it A with 0 findings. It is 100% identical to debugger, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
agentlas-graph
Build an Agentlas automation by describing it, list saved ones, or request a run.
agentlas-orch
Set or show which model runs the orchestrator and which runs the workers.
agentlas-storm
Run a force-robust Stormbreaker loop — route to real agents, execute a verified pipeline to completion.
agentlas-login
Sign this machine into Agentlas (opens the browser sign-in window).
auto-canary
배포 검증 — build, E2E, 브라우저 건강 검진을 실행합니다.
auto-setup
프로젝트 컨텍스트 생성 — 코드베이스를 분석하고 ARCHITECTURE.md 및 .autopus/project 문서를 생성합니다.