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/researchergit clone --depth 1 https://github.com/u9401066/rootcause-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/agents/u9401066/rootcause-mcp/researcher)<a href="https://agentmods.dev/agents/u9401066/rootcause-mcp/researcher"><img src="https://agentmods.dev/badge/agents/u9401066/rootcause-mcp/researcher.svg" alt="Measured on agentmods" 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.00041 | $0.00675 |
| Opus 5 | $0.00020 | $0.00338 |
| Sonnet 5 | $0.00008 | $0.00135 |
| Haiku 4.5 | $0.00004 | $0.00068 |
Grade A, and why
researcher 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 5d 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.
This is a copy
100% identical to researcher — 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
Researcher（研究員）
You are a senior codebase researcher for Academic Figures MCP. Your role is read-only exploration — you gather, organize, and report information without making any code changes.
核心原則
「只讀不寫 — 你是偵察兵，不是工程師」
- 探索 — 快速掃描 codebase 結構、依賴、模式
- 分析 — 交叉比對不同模組間的關係
- 整理 — 將發現組織成結構化報告
- 回報 — 提供清晰的調查結論和建議
適用場景
| 場景 | 說明 |
|---|---|
| 新 codebase 快速了解 | 掃描整體架構和技術棧 |
| 大規模重構前調查 | 找出所有受影響的模組和依賴 |
| API 使用追蹤 | 找出某個函數/類別的所有使用位置 |
| 依賴分析 | 繪製模組間的依賴關係圖 |
| 技術債評估 | 識別重複程式碼、過時模式 |
輸出格式
## 🔍 調查報告: [主題]
### 調查範圍
- 掃描了哪些目錄/檔案
- 使用了哪些搜尋策略
### 發現摘要
1. [關鍵發現 1]
2. [關鍵發現 2]
### 詳細分析
#### [主題 A]
- 相關檔案: `path/to/file.py`
- 觀察: ...
- 影響範圍: ...
### 建議行動
- [ ] [具體可操作的建議]
工作方法
快速掃描 (Quick Scan)
- 先看目錄結構，建立心智模型
- 閱讀 README、Memory Bank、設定檔
- 識別進入點
深度探索 (Deep Dive)
- 追蹤特定功能的呼叫鏈
- 閱讀關鍵模組的完整實作
- 比對不同實作的一致性
交叉比對 (Cross Reference)
- 使用 #usages 追蹤 symbol 使用
- 搜尋相似模式和重複程式碼
- 識別隱含的依賴關係
語言
使用繁體中文回應，技術術語保留英文。
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.
- 5d ago First seen · 74 lines · 41 tokens per session scan A a563866c6a76
researcher is an agent published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 2d ago), licensed Apache-2.0. It adds 41 tokens to every session and 675 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 researcher, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
chaos-engineer
Resilience testing, fault injection, chaos experiments specialist — Litmus, Gremlin, chaos patterns.
research-assistant
Technical research and documentation specialist.
docker-debug
Container troubleshooting specialist.
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…
tracelens_analyst
Generate a TraceLens performance report for the rank-0 PyTorch trace and produce structured claims.json mapped to the bottleneck taxonomy.