An error-investigation command that follows an error through matching code paths, logs, functions, and callers.

Use it to locate the originating file, function, and line; reconstruct the call chain; review occurrences from ingested logs; and investigate likely causes.

It reduces the manual work of connecting an error message or log entry to its source and possible triggers.

How suitable-adventures/suitable-loop configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to suitable-adventures/suitable-loop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/suitable-adventures/suitable-loop/main/.claude/commands/debug-error.md

Clone the repo

git clone --depth 1 https://github.com/suitable-adventures/suitable-loop

Made for: Claude Code.

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

README.md

[![agentmods](https://agentmods.dev/badge/commands/suitable-adventures/suitable-loop/debug-error/github.svg)](https://agentmods.dev/commands/suitable-adventures/suitable-loop/debug-error)

Your own site

<a href="https://agentmods.dev/commands/suitable-adventures/suitable-loop/debug-error"><img src="https://agentmods.dev/badge/commands/suitable-adventures/suitable-loop/debug-error/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/suitable-adventures/suitable-loop/debug-error"><img src="https://agentmods.dev/badge/commands/suitable-adventures/suitable-loop/debug-error.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 182 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00182
Opus 5.5	$0.00000	$0.00073
Sonnet 5.5	$0.00000	$0.00036
Haiku 4.5	$0.00000	$0.00018

Measured 2mo ago against content hash cdde352c4ccf, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

.claude/commands/debug-error.md · 16 lines

What it actually says

Help me investigate this error: $ARGUMENTS

Steps:

Use correlate_error with the provided error text to find matching code paths
If a log file path was provided instead, use ingest_logs first, then get_error_groups
For each relevant error group, use error_detail to get full tracebacks and affected functions
Use query_entity on the key functions in the stack trace to understand their role
Use find_callers on the originating function to see all code paths that lead to it

Then give me:

Where the error originates (file, function, line)
The full call chain leading to the error
How many times this error has occurred (if logs were ingested)
All code paths that could trigger this error
Suggested investigation steps or likely root cause

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.

2mo ago First seen · 16 lines · 0 tokens per session scan A cdde352c4ccf

Subscribe to this mod's changes

debug-error is a command published in the GitHub repository suitable-adventures/suitable-loop (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 182 tokens. 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.

Debugging

debug-error next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
debug-errorsuitable-adventures/suitable-loop	Command	0	7mo ago	MIT	A	0	Claude Code
qa-changesOpenHands/extensions	Command	176	yesterday	MIT	A	63	Claude Code
react-nativegetsentry/toolkit	Command	957	yesterday	none	A	0	Claude Code
auditar-cascadingluanpdd/kit-mcp	Command	5	4d ago	MIT	A	54	Claude Code
http-serviceMadAppGang/magus	Command	14	yesterday	MIT	A	27	Claude Code
doctordoncheli/don-cheli-sdd	Command	59	2mo ago	Apache-2.0	A	76	Claude Code
doctorfatihkan/badi	Command	7	1mo ago	MIT	A	0	Claude Code

suitable-loop: Command for Claude Code