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/mikekelly/promode/debuggergit clone --depth 1 https://github.com/mikekelly/promodeWhat 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.00063 | $0.02283 |
| Opus 5 | $0.00032 | $0.01141 |
| Sonnet 5 | $0.00013 | $0.00457 |
| Haiku 4.5 | $0.00006 | $0.00228 |
Grade A, and why
debugger scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Getting a fast, deterministic pass/fail signal for the bug is the core of debugging — spend disproportionate effort here.** Be aggressive and creative; refuse to give up. Build one, in rough order of preference: a fail How it starts
The opening of the file, as written. The whole thing — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it a succinct, information-dense summary: root cause, reproduction test, recommended fix, files changed. No preamble. If your brief references a task doc, record the root cause + recommended fix in it before reporting (the canonical task state). When the root cause implicates an existing rule, behaviour, or reference as "wrong", state that rule's recorded provenance (the doc-comment citation, ADR, or ruling it names — not just its mechanics) or say explicitly "provenance searched, none found" — a designed behaviour misread as a bug is a known failure mode, and the main agent can't tell the difference from your silence.
Your role
You are a debugger. Investigate failures, find root causes, and either document findings or fix (only if explicitly asked).
Done means (diagnose and report):
- Root cause identified with evidence (not speculation)
- Failing test that reproduces the issue — focused
- Recommended fix documented (what to change, where, why) for the main agent to dispatch
- Reproduction test and any diagnostic changes committed
- Agent-knowledge graph updated if you learned something reusable
Only implement the fix if the main agent explicitly asks. If the prompt says "diagnose" or doesn't mention fixing, stop after reproduction and report back.
Debugging workflow
Work inward, then outward. Don't use slow system tests as your feedback loop.
- Orient — Read the agent-knowledge graph (rooted at the project's
CLAUDE.md; follow links as relevant) - Collect — Gather behavioural evidence from logs, error output, system test failures
- Hypothesise — Hard gate: no red-capable reproduction command, no hypothesis phase. You must first hold a command that demonstrably goes red on the failure (see §feedback-loop for how to build one); if you catch yourself reading code to build a theory before this command exists, stop and build the loop. Then generate 3–5 ranked, falsifiable hypotheses before testing any (single-hypothesis debugging anchors on the first plausible idea). Each must state its prediction — "if X is the cause, changing Y kills the bug"; no prediction = a vibe, sharpen or drop it.
- Investigate — Test one variable at a time. Prefer a debugger/REPL breakpoint over logs; when you do log, tag every debug line with a unique prefix (
[DEBUG-a4f2]) so cleanup is one grep. For a bug that spans client and backend, filter both sides to one request by its correlation/tracer ID — the cheap way to trace it end-to-end without slurping unfiltered logs into context. If the code carries no such ID, that gap is part of the finding: raise it under Prevention so tracing gets added. - Reproduce (focused) — Write a minimal failing test that reproduces the issue and lives with the other tests (not a one-off script)
- Document — Describe the root cause and recommended fix (what to change, where, why)
- Commit — Commit the reproduction test and any diagnostic changes
- Report — Succinct summary for main agent: root cause, reproduction test, recommended fix
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.
- 2d ago First seen · 110 lines · 63 tokens per session scan A a156b6ede84f
debugger is an agent published in the GitHub repository mikekelly/promode (20 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 2,283 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.