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 skills add subhansh-dev/agent-maxxing --skill workflow-debugginggit clone --depth 1 https://github.com/subhansh-dev/agent-maxxingWrote 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/skills/subhansh-dev/agent-maxxing/workflow-debugging)<a href="https://agentmods.dev/skills/subhansh-dev/agent-maxxing/workflow-debugging"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/workflow-debugging/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/skills/subhansh-dev/agent-maxxing/workflow-debugging"><img src="https://agentmods.dev/badge/skills/subhansh-dev/agent-maxxing/workflow-debugging.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.00015 | $0.00398 |
| Opus 5 | $0.00008 | $0.00199 |
| Sonnet 5 | $0.00003 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
workflow-debugging 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 5d 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
Multi-Agent Workflow: Debugging a Production Issue
Systematically debug a production issue using the debugging chain.
Skills Used
| Skill | Role |
|---|---|
| Debugging Patterns | Systematic methodology |
| Execution Protocol | Problem-solving chain |
| Runtime Verify | Run and observe |
| Code Review Checklist | Verify fix |
Workflow
Step 1: Reproduce
Load Execution Protocol skill.
Run the code. Hit the error. See it yourself.
Don't guess — observe.
Step 2: Read the Error
Read the COMPLETE error message.
Extract: error type, file:line, stack trace, context.
Note: what was the user doing when it failed?
Step 3: Bisect
Load Debugging Patterns skill.
Comment out half the code. Does it still happen?
Binary search through the codebase.
Log state at each step.
Step 4: Trace the Flow
Follow the data from input to output.
Where does it go wrong?
Check: async timing, null values, state mutations.
Add console.log at each step.
Step 5: Fix and Verify
Load Runtime Verify skill.
Apply the fix.
Run the app. Drive the changed path.
Push on it: try edge cases, wrong inputs.
Verdict: PASS / FAIL
Step 6: Prevent Recurrence
Load Code Review Checklist.
Add a test case for the bug.
Check: does this pattern exist elsewhere?
Update documentation if needed.
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.
- 5d ago First seen · 73 lines · 15 tokens per session scan A 170b13610875
workflow-debugging is a skill published in the GitHub repository subhansh-dev/agent-maxxing (2 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 398 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
codegraph
Analyze indexed codebases via graph database (neug) and vector index (zvec). Covers call graphs, dependencies, dead code, hotspots, module coupling, architecture reports, semantic search, impact analysis, bug root cause from GitHub issues, class diagrams (UML), and PR review (risk scoring, conflict detection…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
memory-leak-debug
Diagnose memory leaks in the Qwen Code CLI using heap snapshots and the chrome-devtools CLI. Use when investigating high memory usage, unbounded growth, or suspected object retention issues.
bugfix
Fix a bug from a GitHub issue, following the reproduce-first workflow. Use when the user asks to fix a bug, investigate a GitHub issue, or debug a user-reported problem. Takes a GitHub issue URL or number as input.
rust-check
Run cargo check on the current Rust project to find compile errors.