autoresearch:debug

An autonomous bug-finding command that investigates a codebase using structured techniques such as tracing, pattern searches, binary search, or minimal reproductions.

In plain words
What is it for?
Use it to investigate a symptom, limit the search to selected files, choose an investigation technique, filter by severity, or automatically continue into a fixing command.
Why use it?
It helps find multiple bugs systematically instead of stopping after the first one. An optional flag can move from finding bugs to fixing them.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/hi0001234d/coding-agent-mcp-tools/debug
Clone the repo
git clone --depth 1 https://github.com/hi0001234d/coding-agent-mcp-tools

Made for: Claude Code.

Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 432 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00432
Opus 5 $0.00014 $0.00216
Sonnet 5 $0.00005 $0.00086
Haiku 4.5 $0.00003 $0.00043

Measured 2d ago against content hash 97524b89389c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

autoresearch: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 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.

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.

.claude/commands/autoresearch/debug.md · 32 lines

What it actually says

EXECUTE IMMEDIATELY — do not deliberate, do not ask clarifying questions before reading the protocol.

Argument Parsing (do this FIRST)

Extract these from $ARGUMENTS — the user may provide extensive context alongside flags. Ignore prose and extract ONLY flags/config:

  • --fix — if present, auto-switch to /autoresearch:fix after finding bugs
  • --scope <glob> or Scope: — file globs to investigate
  • --symptom "<text>" or Symptom: — description of what's broken
  • --severity <level> — minimum severity to report (critical/high/medium/low)
  • --technique <name> — force a specific investigation technique (binary-search, differential, minimal-reproduction, trace, pattern-search, working-backwards, rubber-duck)
  • Iterations: or --iterations N — integer for bounded mode (CRITICAL: run exactly N iterations then stop)

If Iterations: N or --iterations N is found, set max_iterations = N. Track current_iteration starting at 0. After iteration N, print final summary and STOP.

All remaining text in $ARGUMENTS is additional context — use it to understand the problem but do not treat it as flags.

Execution

  1. Read the debug workflow: .claude/skills/autoresearch/references/debug-workflow.md
  2. If scope or symptom is missing — use AskUserQuestion with batched questions per debug-workflow.md
  3. Execute the 7-phase debug loop
  4. If bounded: after each iteration, check current_iteration < max_iterations. If not, STOP and print summary.

Stream all output live — never run in background.

Changes

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.

  1. 2d ago First seen · 32 lines · 27 tokens per session scan A 97524b89389c

Subscribe to this mod's changes

autoresearch:debug is a command published in the GitHub repository hi0001234d/coding-agent-mcp-tools (11 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 432 once invoked, about $0.0001 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.