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/hi0001234d/coding-agent-mcp-toolsWrote 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/hi0001234d/coding-agent-mcp-tools/debug)<a href="https://agentmods.dev/commands/hi0001234d/coding-agent-mcp-tools/debug"><img src="https://agentmods.dev/badge/commands/hi0001234d/coding-agent-mcp-tools/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/hi0001234d/coding-agent-mcp-tools/debug"><img src="https://agentmods.dev/badge/commands/hi0001234d/coding-agent-mcp-tools/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.00027 | $0.00432 |
| Opus 5.5 | $0.00011 | $0.00173 |
| Sonnet 5.5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00003 | $0.00043 |
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 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.
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>orScope:— file globs to investigate--symptom "<text>"orSymptom:— 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
- Read the debug workflow:
.claude/skills/autoresearch/references/debug-workflow.md - If scope or symptom is missing — use
AskUserQuestionwith batched questions per debug-workflow.md - Execute the 7-phase debug loop
- If bounded: after each iteration, check
current_iteration < max_iterations. If not, STOP and print summary.
Stream all output live — never run in background.
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 · 32 lines · 27 tokens per session scan A 97524b89389c
autoresearch:debug is a command published in the GitHub repository hi0001234d/coding-agent-mcp-tools (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 432 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-31.
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…
react-native
Command "react-native" from getsentry/toolkit, covering examples, also associate with a release and distribution(s), xcode build step (react-native xcode) and important notes.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.
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.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.