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/brain-bootstrap/claude-code-brain-bootstrapWrote 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/commands/brain-bootstrap/claude-code-brain-bootstrap/debug)<a href="https://agentmods.dev/commands/brain-bootstrap/claude-code-brain-bootstrap/debug"><img src="https://agentmods.dev/badge/commands/brain-bootstrap/claude-code-brain-bootstrap/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/commands/brain-bootstrap/claude-code-brain-bootstrap/debug"><img src="https://agentmods.dev/badge/commands/brain-bootstrap/claude-code-brain-bootstrap/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.00019 | $0.00678 |
| Opus 5.5 | $0.00008 | $0.00271 |
| Sonnet 5.5 | $0.00004 | $0.00136 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
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 1mo 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug a failing test, build, or service issue: $ARGUMENTS
ultrathink — use extended reasoning for root cause analysis.
Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST
Symptom fixes are failure. A fix that makes a test pass without understanding why it was failing is not a fix — it is a masked bug. This law is especially critical under time pressure, after 2+ failed fix attempts, or when there is a "just try this quick thing" temptation.
4 Phases (do not skip or reorder):
- Root Cause — gather all evidence, classify the failure
- Hypothesis — form a specific, testable hypothesis about the cause
- Fix Design — design a minimal fix that addresses the root cause only
- Verification — run the test/build, confirm fix, check for regressions
Instructions
Read claude/tasks/lessons.md for known pitfalls before starting.
Phase 1 — Root Cause (gather ALL evidence before hypothesizing):
-
Identify the failure type from the arguments:
- Test failure → read test file + source under test
- Build failure → read error output, check compiler/bundler errors
- Runtime error → read logs, check DB state, check message queues
- Lint error → run linter on the file
-
Gather evidence (do ALL of these before proposing a fix):
- Read the full error message/stack trace
- Read the failing source file
- Check if the error is pre-existing:
git stash && <run-test> && git stash pop - Search
claude/tasks/lessons.mdfor similar past issues - Check if the file was recently modified:
git --no-pager log --oneline -5 -- <file>
Phase 2 — Hypothesis (form one specific, testable hypothesis before acting):
Write it explicitly: "I believe the root cause is X because Y."
Phase 3 — Fix Design (fix only the root cause, no opportunistic changes):
- Diagnose root cause — classify:
Category Symptoms Typical fix Missing import ReferenceError,is not definedAdd import statement Type mismatch TypeError,Cannot read propertiesFix type/null check DB schema drift column X does not existCheck migration Stale build Works after clean build Clean + rebuild Stub mismatch Test assertion fails Verify stub key matches export name
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.
- 1mo ago First seen · 67 lines · 19 tokens per session scan A e73c646d24fe
debug is a command published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 678 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 commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
fix
Universal debugging and fix application with semantic code analysis.
debug
Systematic 9-step debugging framework. Generate 20+ hypotheses, rank by likelihood, implement most probable fix.