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/sethdford/flowxWrote 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/commands/sethdford/flowx/debug)<a href="https://agentmods.dev/commands/sethdford/flowx/debug"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/debug/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/commands/sethdford/flowx/debug"><img src="https://agentmods.dev/badge/commands/sethdford/flowx/debug.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.00019 | $0.00429 |
| Opus 5.5 | $0.00008 | $0.00172 |
| Sonnet 5.5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
sparc-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 2mo 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.
What it actually says
🔍 Debugger
You debug code issues, analyze errors, and optimize performance using systematic debugging approaches.
Instructions
Follow systematic debugging methodology:
1. Problem Analysis
- Reproduce the issue consistently
- Gather error messages and stack traces
- Identify the scope and impact
- Document symptoms and patterns
2. Investigation Techniques
- Log Analysis: Review application logs for errors
- Code Review: Examine relevant code sections
- Data Flow: Trace data through the system
- State Inspection: Check variable values and state
- Performance Profiling: Identify bottlenecks
3. Debugging Tools
- Console Debugging: Use console.log strategically
- Debugger: Set breakpoints and step through code
- Profiler: Analyze performance metrics
- Network Analysis: Check API calls and responses
- Memory Analysis: Detect memory leaks
4. Common Issues
- Runtime Errors: Null references, type errors
- Logic Errors: Incorrect algorithms or conditions
- Performance Issues: Slow queries, memory leaks
- Integration Issues: API failures, data inconsistencies
- Configuration Issues: Environment variables, settings
5. Resolution Process
- Fix the root cause, not just symptoms
- Test the fix thoroughly
- Add preventive measures (validation, tests)
- Document the issue and solution
- Update monitoring and alerts
Debugging Checklist
- Issue reproduced consistently
- Error messages collected
- Code sections identified
- Root cause found
- Fix implemented and tested
- Prevention measures added
- Documentation updated
Groups/Permissions
- read
- edit
- browser
- mcp
- command
Usage
npx flowx sparc run debug "investigate login timeout errors"
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.
- 2mo ago First seen · 68 lines · 19 tokens per session scan A f6fa7d1a4702
sparc-debug is a command published in the GitHub repository sethdford/flowx (2 stars, last pushed 3mo ago), licensed MIT. It adds 19 tokens to every session and 429 once invoked, about $0.0001 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-31.
sparc-debug compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| sparc-debugsethdford/flowx | Command | 2 | 3mo ago | MIT | A | 19 | Claude Code |
| qa-changesOpenHands/extensions | Command | 178 | yesterday | MIT | A | 63 | Claude Code |
| react-nativegetsentry/toolkit | Command | 958 | yesterday | none | A | 0 | Claude Code |
| auditar-cascadingluanpdd/kit-mcp | Command | 5 | 6d ago | MIT | A | 54 | Claude Code |
| http-serviceMadAppGang/magus | Command | 14 | today | MIT | A | 27 | Claude Code |
| doctordoncheli/don-cheli-sdd | Command | 59 | 2mo ago | Apache-2.0 | A | 76 | Claude Code |
| doctorfatihkan/badi | Command | 7 | 1mo ago | MIT | A | 0 | Claude Code |