Borrowing it
Nothing to install: this file belongs to adrian-d-hidalgo/nestjs-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/adrian-d-hidalgo/nestjs-mcp-server/main/.claude/commands/debug.mdgit clone --depth 1 https://github.com/adrian-d-hidalgo/nestjs-mcp-serverWrote 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/adrian-d-hidalgo/nestjs-mcp-server/debug)<a href="https://agentmods.dev/commands/adrian-d-hidalgo/nestjs-mcp-server/debug"><img src="https://agentmods.dev/badge/commands/adrian-d-hidalgo/nestjs-mcp-server/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/adrian-d-hidalgo/nestjs-mcp-server/debug"><img src="https://agentmods.dev/badge/commands/adrian-d-hidalgo/nestjs-mcp-server/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.00075 | $0.02417 |
| Opus 5.5 | $0.00030 | $0.00967 |
| Sonnet 5.5 | $0.00015 | $0.00483 |
| Haiku 4.5 | $0.00007 | $0.00242 |
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 2mo 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
In every route the debugger agent is the executor of the deep RCA — you do not replicate
its work; you invoke the agent. You load the bug-diagnosis skill as the process guide (the
deprecation check, evidence before assertion, the reproduction ladder, the certainty bar) and the
github-issues skill for the Mode B shape and the authorization contract.
Always propose; never create or comment without authorization.
Rows 5 and 6 are the pair most often confused. The test: does something exist and behave wrongly (bug), or does it not exist (capability)?
- Symptom route: what fails, which export or decorator, which transport, expected vs actual.
- Issue route: reproduction steps, the three versions (
@nestjs-mcp/server,@nestjs/common,@modelcontextprotocol/sdk), the transport, expected vs actual. If a critical piece is missing → propose asking in the issue's comments and do not advance to the RCA until it is answered. - Failing-test route: the full failure output, not the first line.
Once the musts are met, continue and run the diagnosis (via the agent). Never invent or
assume a cause, a reproduction, a duplicate, or a fix. CLAUDE.md: "A fix grounded in
[Inference] is not done — get the evidence or say you couldn't and stop."
Issue route — an existing GitHub issue.
0. Check the workspace — .project/tasks/issue-<N>/notes.md. If it exists, read it before
investigating. It records what was already tried and ruled out; re-running a dead end is the
specific waste it exists to prevent. If spec.md exists too, this issue already has an approved
analysis — say so, because a new RCA may invalidate it.
- Read the issue and its comments (
issue_read,getthenget_comments) — what the reporter describes, in their words. The comments usually carry the versions and the "it also happens when…" that the body lacks. - Judge report sufficiency against the Musts. If a critical piece is missing → propose a
comment asking for it (
add_issue_comment, under authorization — commenting on a public issue is a mutation) and do NOT advance to the RCA until it is answered. Never assume the missing facts. - Light discovery.
search_issuesfor another issue on the same symptom, open and closed. A match → STOP and raise it with a recommendation (add evidence to the existing one vs open a new one); a closed match means a regression — a new issue linking back, never a reopen. Then continue at the Shared close.
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.
- 2mo ago First seen · 143 lines · 75 tokens per session scan A 037d76c24b3a
debug is a command published in the GitHub repository adrian-d-hidalgo/nestjs-mcp-server (40 stars, last pushed 29d ago), licensed MIT. It adds 75 tokens to every session and 2,417 once invoked, about $0.0003 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…
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.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
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.