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 alexeyshishin/as-skill --skill code-debuggit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/alexeyshishin/as-skill/code-debug)<a href="https://agentmods.dev/skills/alexeyshishin/as-skill/code-debug"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/code-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/skills/alexeyshishin/as-skill/code-debug"><img src="https://agentmods.dev/badge/skills/alexeyshishin/as-skill/code-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.00067 | $0.00422 |
| Opus 5.5 | $0.00027 | $0.00169 |
| Sonnet 5.5 | $0.00013 | $0.00084 |
| Haiku 4.5 | $0.00007 | $0.00042 |
Grade A, and why
code-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 4d 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
Skill: /code-debug
ORCHESTRATOR. One debugger subagent. It diagnoses before it touches anything.
Invocation
/code-debug "<error text / failing test / what broke>" (optionally /code-debug <slug> to tie it
to a feature build)
Steps
- Gather the symptom: the error/stack/failing-test name from the user, plus the build
report
swarm-report/<slug>-build.mdif a slug was given. - Spawn 1 debugger (
Task,general-purpose). Prompt:Answer TERSE. Read
.claude/agents/code-debugger.mdand follow it exactly. Symptom: <verbatim error / failing test>. Feature slug (if any): . - Report the debugger's return verbatim: root cause, evidence, fix, and the re-run output.
- Route the outcome:
fixed→ suggest/code-review <slug>to check the fix.root_cause_found(found but not fixed) orstuck→ show the hypothesis ladder; the user decides the fix, or re-run/code-build <slug>with the root cause as input.cannot_reproduce→ ask the user for exact repro steps; do not guess-patch.
Where it sits in the loop
/code-plan → /code-build → /code-review. If a test fails or review says rework → /code-debug →
back to /code-build. The Stop test-gate hook blocks "done" until tests actually run.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago Changed e6e274d2e9fc
- 1mo ago First seen · 30 lines · 67 tokens per session scan A b43f07537deb
code-debug is a skill published in the GitHub repository alexeyshishin/as-skill (5 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 422 once invoked, about $0.0003 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.
Other skills, from other repositories
memorb-lint
Wiki Lint workflow: a health check over the memory vault that surfaces contradictions, stale pages, orphans, missing pages, broken wikilinks, and bare internal paths. Offer to run it before dream-studio or after manual moves/renames. Triggers: tidy up memory, check the second brain, health check, fix links, moved…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
spark-engineer
Use when writing Spark jobs, debugging performance issues, or configuring cluster settings for Apache Spark applications, distributed data processing pipelines, or big data workloads. Invoke to write DataFrame transformations, optimize Spark SQL queries, implement RDD pipelines, tune shuffle operations, configure…
debugging-wizard
Parses error messages, traces execution flow through stack traces, correlates log entries to identify failure points, and applies systematic hypothesis-driven methodology to isolate and resolve bugs. Use when investigating errors, analyzing stack traces, finding root causes of unexpected behavior, troubleshooting…
log-analyzer
A log-analysis helper that reads application and system logs to find unusual patterns and likely causes. Logs are records of events such as errors, requests, warnings, and service activity.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.