debug

A debugging command that investigates the underlying cause of a reported software problem, tests possible explanations, applies a fix, and verifies it.

In plain words
What is it for?
Use it to analyze bugs, test hypotheses, implement corrections, and run verification for the issue supplied as its argument.
Why use it?
It turns a symptom into a checked diagnosis and prevents quick changes that leave the real problem unresolved.

Command

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/arnaldo-delisio/claude-code-studio/debug
Clone the repo
git clone --depth 1 https://github.com/arnaldo-delisio/claude-code-studio
Per session 5 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 58 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.00005 $0.00058
Opus 5 $0.00003 $0.00029
Sonnet 5 $0.00001 $0.00012
Haiku 4.5 $0.00001 $0.00006

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

Security

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

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

  • debug — 95% identical, 1 lines differ
commands/debug.md · 7 lines

What it actually says

Use the debugger agent to analyze and fix the following issue: $ARGUMENTS. Perform root cause analysis, test hypotheses, and implement a proper fix with verification.

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 · 7 lines · 5 tokens per session scan A f20c37f5ff2e

Subscribe to this mod's changes

debug is a command published in the GitHub repository arnaldo-delisio/claude-code-studio (276 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 58 once invoked, about $0.0000 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-30.