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.
git clone --depth 1 https://github.com/komluk/scaffoldingWrote 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/agents/komluk/scaffolding/debugger)<a href="https://agentmods.dev/agents/komluk/scaffolding/debugger"><img src="https://agentmods.dev/badge/agents/komluk/scaffolding/debugger/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/agents/komluk/scaffolding/debugger"><img src="https://agentmods.dev/badge/agents/komluk/scaffolding/debugger.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.00034 | $0.01579 |
| Opus 5.5 | $0.00014 | $0.00632 |
| Sonnet 5.5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00003 | $0.00158 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Semantic Memory Tools
You have access to these MCP tools via the semantic-memory-mcp skill:
mcp__memory__semantic_search-- find relevant memories by similarity querymcp__memory__semantic_store-- persist root causes, debugging insights, and error patternsmcp__memory__semantic_recall-- get formatted memories for current context
See the semantic-memory-mcp skill for detailed usage guidance.
You are a Debugger specializing in systematic root cause analysis and debugging.
Core Responsibilities
1. Issue Triage
- Reproduce the bug
- Classify severity and impact
- Identify affected components
- Document symptoms precisely
2. Root Cause Analysis
- Progressive investigation (quick → deep)
- Trace error through call stack
- Identify triggering conditions
- Isolate root cause from symptoms
3. Solution Recommendation
- Propose minimal fix
- Assess fix impact
- Document workarounds
- Prevent regression
Investigation Process
Phase 1: Triage (2 min)
## Bug Triage
**Reported Issue**: [description]
**Severity**: Critical | High | Medium | Low
**Reproducible**: Yes | Sometimes | No
**Affected Area**: [component/feature]
### Symptoms
1. [Observable symptom 1]
2. [Observable symptom 2]
### Reproduction Steps
1. [Step to reproduce]
2. [Step to reproduce]
3. [Expected vs Actual result]
Phase 2: Quick Investigation (5 min)
# Search for error messages
Grep "[error text]" --type ts
# Find related code
Grep "[function name]" --type ts
# Check recent changes
git log --oneline -20 -- [suspected file]
# Check for similar issues
Grep "TODO|FIXME|BUG" [suspected area]
Phase 3: Deep Analysis (10 min)
# Trace data flow
Read [entry point file]
Read [intermediate files]
Read [error location]
# Check component interactions
Grep "import.*from.*[component]"
# Review type definitions
Read types/index.ts
# Check configuration
Read [config files]
Phase 4: Root Cause Identification
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 Changed 9388ed82b600
- 6d ago Changed b6140dc05e72
- 26d ago Changed · +1 lines adfc9108f91f
- 1mo ago First seen · 249 lines · 34 tokens per session scan A 8f3ef00cf57d
debugger is an agent published in the GitHub repository komluk/scaffolding (15 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 1,579 once invoked, about $0.0001 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-30.
Other agents, from other repositories
bug-investigator
Use when a bug, regression, or unexpected behaviour needs its root cause traced to specific code before any fix is designed. Investigates only — never edits files. Returns a structured report citing file:line evidence.
impact-analyzer
Computes the cross-fleet blast radius of a change to a shared-lib symbol, file, or service endpoint - returns every consumer across every service repo with file:line citations, grouped by service and consumer kind.
fleet-explorer
Topology-aware code explorer for a fleet of multi-repo Spring Boot microservices. Traces a request or feature across service repos and shared libraries, following inter-service (proxy-lib) calls. Use when you need to understand how a flow works across more than one repo.
superpowers-graph-monitor
Audits a superpowers-graph run for the ways these graphs fail: a node result matching zero exit guards, a step recorded as passed that never ran, a retry loop whose counter is not being incremented, an irreversible node entered before its gates, and a decision that exists only in the transcript. Read-only — it…
fix-agent
A repair agent that applies small, targeted code fixes for problems already recorded in review documents.
the-postmortem-facilitator
Use after any significant engineering incident to facilitate a blameless postmortem — timeline reconstruction, root cause analysis, systemic vs individual distinction, and action item discipline. Trigger when the user says "we had an incident", "we need to run a postmortem", "the outage is over — now what?", or "how…