amelia: Command for Claude Code

.claude/commands/sp-debug.md

sp-debug is a command for Claude Code from existential-birds/amelia. It costs 7 tokens per session (151 once invoked), scanned A, original, Apache-2.0.

A command that guides a step-by-step debugging process: reproduce the problem, inspect evidence, test likely causes, make the smallest fix, and verify the result.

In plain words
What is it for?
Use it to investigate errors in code, logs, or runtime behavior, test competing explanations, apply a fix, and check for regressions.
Why use it?
It reduces guesswork and helps distinguish the actual cause of a bug from its visible symptoms.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is existential-birds/amelia's own configuration. It tells Claude Code how to work on amelia itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything amelia configures →

Reuse

Borrowing it

Nothing to install: this file belongs to existential-birds/amelia. 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/existential-birds/amelia/main/.claude/commands/sp-debug.md
Clone the repo
git clone --depth 1 https://github.com/existential-birds/amelia

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.

agentmods badge for sp-debug

README.md
[![agentmods](https://agentmods.dev/badge/commands/existential-birds/amelia/sp-debug/github.svg)](https://agentmods.dev/commands/existential-birds/amelia/sp-debug)
Your own site
<a href="https://agentmods.dev/commands/existential-birds/amelia/sp-debug"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/sp-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.

agentmods 80×15 button for sp-debug

Your own site · 80×15
<a href="https://agentmods.dev/commands/existential-birds/amelia/sp-debug"><img src="https://agentmods.dev/badge/commands/existential-birds/amelia/sp-debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 151 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00007 $0.00151
Opus 5.5 $0.00003 $0.00060
Sonnet 5.5 $0.00001 $0.00030
Haiku 4.5 $0.00001 $0.00015

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

Security

Grade A, and why

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

.claude/commands/sp-debug.md · 17 lines

What it actually says

Follow a systematic debugging workflow for this problem:

$ARGUMENTS

Systematic Debugging Process

  1. Reproduce the issue - Confirm you can observe the problem
  2. Gather information - Read error messages, logs, and relevant code
  3. Form hypotheses - List 2-3 possible causes ranked by likelihood
  4. Test hypotheses - Add logging/debugging to verify or eliminate each
  5. Identify root cause - Trace the actual cause, not just symptoms
  6. Implement fix - Make the minimal change to fix the issue
  7. Verify fix - Confirm the problem is resolved and no regressions
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. 1mo ago First seen · 17 lines · 7 tokens per session scan A 5c8fdef9dec7

Subscribe to this mod's changes

sp-debug is a command published in the GitHub repository existential-birds/amelia (21 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 151 once invoked, about $0.0000 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.