Borrowing it
Nothing to install: this file belongs to rex/mcp-apple-reminders. 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/rex/mcp-apple-reminders/main/.claude/commands/debug.mdgit clone --depth 1 https://github.com/rex/mcp-apple-remindersWrote 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/rex/mcp-apple-reminders/debug)<a href="https://agentmods.dev/commands/rex/mcp-apple-reminders/debug"><img src="https://agentmods.dev/badge/commands/rex/mcp-apple-reminders/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/rex/mcp-apple-reminders/debug"><img src="https://agentmods.dev/badge/commands/rex/mcp-apple-reminders/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.00013 | $0.00204 |
| Opus 5.5 | $0.00005 | $0.00082 |
| Sonnet 5.5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00001 | $0.00020 |
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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debug — 100% identical, 0 lines differ
What it actually says
Debug: $ARGUMENTS
- If a failing test was given, run it and capture the exact output first.
- Spawn
debuggersubagent with the error, repro steps, and relevant file paths. debuggerreturns: symptom / root cause / evidence / fix / verification.- If
debuggercan't find root cause in 5 hypotheses, STOP and report. - If the fix is applied, spawn
test-runnerto verify.
Escalate to Opus (debugger with model: opus) if the repro fails twice.
Never fix symptoms. If the fix is "catch the exception" or "skip the test," stop and ask the human.
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 · 20 lines · 13 tokens per session scan A 3dac4f3acf0c
debug is a command published in the GitHub repository rex/mcp-apple-reminders (3 stars, last pushed 25d ago), licensed MIT. It adds 13 tokens to every session and 204 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
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
error-analysis
Analyze errors and incidents to find root causes and fixes.
doctor
Diagnose a broken llm-router setup.
types
Debug and fix TypeScript type errors with systematic analysis and expert guidance.
verify-upgrade
Verify Spring Boot project upgrade readiness with parallel multi-skill analysis.
audit
Audit closed tickets for regressions against today's code (unchanged, evolved, implemented wrong, not implemented), plus duplicate and groupable open ones.