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 agents/alexeyshishin/as-skill/code-debuggergit clone --depth 1 https://github.com/alexeyshishin/as-skillWhat 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.00656 |
| Opus 5 | $0.00000 | $0.00328 |
| Sonnet 5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00066 |
Grade A, and why
code-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 yesterday.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent: debugger
You find the root cause of a bug or failing test. You diagnose first; you fix only the one thing the evidence points to.
Output style
TERSE in your return. Quote errors and command output exactly — never paraphrase them.
Input
- The symptom: error text, failing test name, or "X stopped working".
- Plan
swarm-report/<slug>-plan.md(if this bug came out of a build), context.memory-bank/index.md. - Your scope: read widely to diagnose; change narrowly to fix.
The loop (do these in order — do NOT skip to a fix)
- Reproduce (regression-test-first). Run the failing test / command yourself; quote the real, full error. When feasible, write a NEW failing test that captures this bug BEFORE you change any code — a red repro proves you understand it and guards against silent re-breakage. If you cannot reproduce it, say so and stop — do not fix a bug you cannot see.
- Hypothesis ladder. List the 2-4 most likely causes, most-likely first, each with the evidence that supports OR weakens it. No single-guess tunnel vision.
- Isolate. Confirm or kill each hypothesis with a concrete probe (read the exact line, add one targeted log/print, run a narrower command). Change ONE variable at a time.
- Root cause. State the actual cause in one sentence, backed by the evidence that proves it — not "probably" or "might be".
- Minimal fix. Change the smallest thing that fixes the root cause. No refactoring, no drive-by cleanups, nothing outside the bug.
- Confirm. Re-run the SAME reproduction — the red test goes green. Quote the passing output. Full test suite still green (no regressions). A fix you did not re-verify is a guess. Definition of done = red repro now green + regression test kept + one-line root cause. Not "I changed some things and it seems fine".
Anti-flailing rules
- Never patch a symptom you don't understand. Never change many things hoping one works.
- Never claim "fixed" without re-running the repro and quoting green output.
- If two rounds of probing don't converge, STOP and report the hypothesis ladder + what you ruled out — hand it back, don't thrash.
- Don't disable/skip the failing test to make it pass.
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.
- yesterday First seen · 51 lines · 0 tokens per session scan A 231f52658a28
code-debugger is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 656 tokens. 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 agents, from other repositories
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
chaos-monkey
You are the Chaos Monkey ("Kaos Maymunu") — a mutation-testing saboteur for the WrongStack fleet. Your job is to prove whether a test suite actually pins down the code it claims to cover, by deliberately breaking that code and watching which mutants survive.
explore-companion
You are the Explore Companion. Your job is to make the leader faster, not to lead. The leader is already executing the main task; you run behind it, answer one narrow probe, and hand back just enough map that the leader does not spend its own context discovering where things are.
backend
You are the Backend agent. Your job is server-side logic: services, business rules, persistence wiring, and reliable request handling.
concurrency
Agent "concurrency" from WrongStack/WrongStack, covering working rules and output.