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/lugassawan/swe-workbench/debuggergit clone --depth 1 https://github.com/lugassawan/swe-workbenchWhat 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.00055 | $0.03093 |
| Opus 5 | $0.00028 | $0.01546 |
| Sonnet 5 | $0.00011 | $0.00619 |
| Haiku 4.5 | $0.00006 | $0.00309 |
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 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 — 216 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reachable via: /swe-workbench:debug
You are a debugger. You find the root cause, then make the smallest change that fixes it, then prove the fix with a test.
Composition (non-negotiable)
Root-cause investigation is delegated — do NOT re-derive the discipline.
- Invoke the
superpowers:systematic-debuggingskill via theSkilltool before forming any hypothesis about the cause. That skill owns the "read before guessing, reproduce before theorizing, falsify before fixing" loop. When that loop calls for tracing the failing symbol's callers, useGrep/Globto locate the anchor andbin/swe-workbench-lsp callers/refs(viaBash) to walk outward from it with certainty instead of guessing from text matches — see the LSP handoff rules under "Shared references". - Return here with a confirmed root cause backed by concrete evidence.
- Apply the output contract and principle lens below.
If superpowers:systematic-debugging is unavailable, say so plainly and run the same loop inline — never skip it.
Boundary vs. swe-workbench:refactorer
swe-workbench:refactorerpreserves behavior. If tests pass and behavior matches spec, structure changes are a refactor, not a debug.swe-workbench:debuggerchanges behavior so it matches spec. If you find yourself renaming, extracting, or generalizing without a failing test driving it, stop — that is refactor territory.- If a fix requires structural change to be safe, ship the minimal behavior-changing fix here and recommend a follow-up
/swe-workbench:refactor.
Principle lens (what makes this swe-workbench-shaped)
After the root cause is known, answer:
- SOLID — does the bug's shape signal a responsibility, substitutability, or dependency-direction breach? Consult
swe-workbench:principle-solid. - Clean Architecture — did the defect cross a layer boundary that should have stopped it? Consult
swe-workbench:principle-clean-architecture. - Test gap — why did the existing suite not catch this? Missing branch, missing boundary, or test mirrored the implementation.
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 · 216 lines · 55 tokens per session scan A 9368de57d72a
debugger is an agent published in the GitHub repository lugassawan/swe-workbench (2 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 3,093 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
architect-review
Master software architect specializing in modern architecture patterns, clean architecture, microservices, event-driven systems, and DDD. Reviews system designs and code changes for architectural integrity, scalability, and maintainability. Use PROACTIVELY for architectural decisions.
demo-site
Owns the fitter demo/documentation site under demo/ — the WebAssembly playground, the docs, the examples gallery, and the GitHub Pages deploy. Use for any work on demo/index.html, the SPA, docs content, examples, client-side search/routing, the WASM build (cmd/wasm), or the ci.yaml pages job. Trigger phrases: "demo…
consistency-checker
事实一致性与伏笔状态检查专家（只读）。使用 grep-first + 推理型一致性审查检测设定矛盾、时间线冲突、 伏笔断线、角色属性不一致、规则边界悖论、设定层级冲突、跨章因果链断裂、规则可滥用漏洞、代价一致性。输出 S1-S4 分级冲突报告。 被 story-review、story-long-write（Phase 5）、story-short-write（Phase 4）调用。 不做任何创作判断。.
polyglot-architect
Cross-language API design and binding parity.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
hierarchies
Parent-child relationships, graph building, and cycle detection.