Borrowing it
Nothing to install: this file belongs to mort-lab/excel-mcp. 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/mort-lab/excel-mcp/main/.claude/commands/development/debug-RCA.mdgit clone --depth 1 https://github.com/mort-lab/excel-mcpWrote 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/mort-lab/excel-mcp/debug-rca)<a href="https://agentmods.dev/commands/mort-lab/excel-mcp/debug-rca"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/debug-rca/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/mort-lab/excel-mcp/debug-rca"><img src="https://agentmods.dev/badge/commands/mort-lab/excel-mcp/debug-rca.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.00000 | $0.00592 |
| Opus 5.5 | $0.00000 | $0.00237 |
| Sonnet 5.5 | $0.00000 | $0.00118 |
| Haiku 4.5 | $0.00000 | $0.00059 |
Grade A, and why
debug-RCA scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Test with curl/Postman first This is a copy
100% identical to debug-RCA — 220 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Issue
Systematically debug and diagnose the reported problem.
Problem Description
$ARGUMENTS
Debugging Process
-
Reproduce the Issue
- Get exact steps to reproduce
- Verify you can see the same problem
- Note any error messages or logs
- Document the expected vs actual behavior
-
Gather Information
# Check recent changes git log --oneline -10 # Look for error patterns in logs # Search for related error messages -
Isolate the Problem
- Binary Search: Comment out code sections to narrow down
- Git Bisect: Find when the bug was introduced
- Logging: Add strategic log statements
- Debugger: Set breakpoints if applicable
-
Common Debugging Strategies
For Runtime Errors
- Read the full stack trace
- Identify the exact line causing the error
- Check variable values at that point
- Verify assumptions about data types
For Logic Errors
- Add print/log statements to trace execution
- Verify each step produces expected results
- Check boundary conditions
- Test with minimal reproducible example
For Performance Issues
- Add timing measurements
- Check for N+1 queries
- Look for inefficient algorithms
- Profile if necessary
For Integration Issues
- Verify external service is accessible
- Check authentication/credentials
- Validate request/response formats
- Test with curl/Postman first
-
Root Cause Analysis
- Why did this happen?
- Why wasn't it caught earlier?
- Are there similar issues elsewhere?
- How can we prevent this class of bugs?
-
Implement Fix
- Fix the root cause, not just symptoms
- Add defensive programming if needed
- Consider edge cases
- Keep fix minimal and focused, follow KISS
-
Verify Resolution
- Confirm original issue is fixed
- Check for regression
- Test related functionality
- Add test to prevent recurrence
-
Document Findings
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 · 109 lines · 0 tokens per session scan A 5e23896bfbe0
debug-RCA is a command published in the GitHub repository mort-lab/excel-mcp (5 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 592 tokens. A static security scan graded it A with 1 finding (makes network calls). It is 100% identical to debug-RCA, differing in 220 lines, and is treated as a copy.
Other commands, from other repositories
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
api-aqa-flow-execution-and-report-analysis
Phase 6 Execution & Report Analysis of api-aqa-flow (USER INTERACTION REQUIRED).
diagnose-deeptrace
Run a ZDX deep trace diagnostics session — start, analyze, or clean up deep traces for a user's device.
troubleshoot-user
Cross-product troubleshooting of user connectivity across ZCC, ZDX, ZPA, and ZIA.
run-agents-for-issues
address all found gaps and issues. start one agent per the problem.
preflight
Diagnostique l'environnement Cortex et guide la réparation (DB, extensions, modèles).