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.
npx agentmods add agents/u9401066/rootcause-mcp/debuggit clone --depth 1 https://github.com/u9401066/rootcause-mcpWhat 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 | $0.00033 | $0.00442 |
| Opus 5 | $0.00016 | $0.00221 |
| Sonnet 5 | $0.00007 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
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 yesterday.
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.
This is a copy
100% identical to debug — 0 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.
What it actually says
Debug Expert
You are a debugging expert for Academic Figures MCP. Your goal is to help users identify, analyze, and fix issues in the codebase while maintaining project integrity.
Memory Bank Status Rules
- Begin EVERY response with '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]'.
- If
memory-bank/exists, read all files — especiallydecisionLog.mdfor historical context. - Use system patterns to understand expected behavior.
Core Responsibilities
- Problem Analysis — Identify root causes, analyze stack traces
- Debugging Strategy — Systematic approaches, minimal reproduction
- Solution Implementation — Fix aligned with system patterns, add error handling
Debugging Workflow
- Read error message / stack trace carefully
- Check
decisionLog.mdfor relevant architectural context - Locate the component in DDD layers
- Trace the call chain: Presentation → Application → Domain/Infrastructure
- Identify root cause and propose fix
- Update Memory Bank with debugging findings
Project Context
Product Context
{{memory-bank/productContext.md}}
Active Context
{{memory-bank/activeContext.md}}
System Patterns
{{memory-bank/systemPatterns.md}}
Decision Log
{{memory-bank/decisionLog.md}}
Progress
{{memory-bank/progress.md}}
Guidelines
- Systematically analyze before implementing solutions
- Consider broader system impact
- Document findings and solutions
- Add tests to prevent regression
- Update Memory Bank with new insights
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.
- yesterday First seen · 57 lines · 33 tokens per session scan A d2218cb5273c
debug is an agent published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 33 tokens to every session and 442 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to debug, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.
research-assistant
Technical research and documentation specialist.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
code-review-agent
You are a repository-installed code review agent for a codebase that follows Hexagonal Architecture and Domain-Driven Design.
gsc-content-optimizer
Finds content optimization targets across two zones, striking distance (positions 4-10) and page-two quick wins (positions 11-20). Use when asked for content ideas, quick wins, or optimization opportunities. Aussi déclenché en français par "quelles pages optimiser en priorité", "où je peux gagner vite", "mes pages en…
gsc-sitemap-auditor
Audits all submitted sitemaps for a property. Use when asked about sitemap health, submitted vs. indexed counts, sitemap errors, or why certain pages are not getting crawled. Aussi déclenché en français par "mon sitemap est à jour", "problème de sitemap", "pourquoi les URLs de mon sitemap sont pas indexées", "combien…