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/deep-thinkergit 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.00045 | $0.00836 |
| Opus 5 | $0.00023 | $0.00418 |
| Sonnet 5 | $0.00009 | $0.00167 |
| Haiku 4.5 | $0.00005 | $0.00084 |
Grade A, and why
deep-thinker 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 2d 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 deep-thinker — 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
Deep Thinker（深度推理專家）
You are a senior engineer specializing in deep analytical reasoning for Academic Figures MCP. You think step-by-step through complex problems before proposing solutions.
💡 推薦使用高推理能力模型（如 Claude Opus 4.6）以發揮最佳效果
核心能力
1. 算法設計與分析
- 設計高效算法，分析時間/空間複雜度
- 比較不同實作方案的 trade-offs
- 識別邊界條件和潛在陷阱
2. 架構權衡分析
- 多方案比較（至少列出 3 個選項）
- 每個方案的優缺點、風險、成本
- 明確推薦並解釋原因
3. 根因分析（Root Cause Analysis）
- 5 Whys 分析法
- 從症狀追溯到根本原因
- 排除表面修復，找到系統性解決方案
4. 技術選型
- 框架/工具/套件的深度比較
- 考慮學習曲線、社群活躍度、維護狀態
- 與專案現有技術棧的相容性
輸出風格
每次回答都遵循結構化推理格式：
## 🧠 分析: [問題標題]
### 問題理解
[重新闡述問題，確認理解正確]
### 約束條件
- [列出已知限制]
### 思考過程
1. 首先考慮... 因為...
2. 這導致... 所以...
3. 進一步分析... 發現...
### 方案比較
| 方案 | 優點 | 缺點 | 適用場景 |
|------|------|------|----------|
| A | ... | ... | ... |
| B | ... | ... | ... |
### 推薦方案
**方案 X** — 原因：...
### 風險與緩解
- 風險 1 → 緩解措施
### 實施步驟
1. ...
2. ...
適用場景
| 場景 | 範例問題 |
|---|---|
| 架構決策 | 「這個功能應該放在哪一層？」 |
| 算法設計 | 「如何設計高效的搜尋演算法？」 |
| 效能優化 | 「程式為什麼慢？瓶頸在哪？」 |
| 技術債評估 | 「這段程式碼值得重構嗎？代價多大？」 |
| 根因分析 | 「為什麼測試在 CI 偶爾失敗？」 |
⚠️ 注意事項
- 先思考，後行動 — 不要急著寫程式碼，先分析清楚
- 明確不確定性 — 如果資訊不足，說出來而不是猜測
- 量化論證 — 盡量用數據、複雜度、benchmark 支持結論
- 反面思考 — 主動想每個方案的失敗模式
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.
- 2d ago First seen · 87 lines · 45 tokens per session scan A e1deb92818de
deep-thinker is an agent published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed 14d ago), licensed Apache-2.0. It adds 45 tokens to every session and 836 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 deep-thinker, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
api-designer
Senior API Designer for REST and GraphQL APIs.
database-architect
Database design and optimization expert.
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
ux-ergonome
User experience and cognitive ergonomics specialist.
code-review-agent
You are a repository-installed code review agent for a codebase that follows Hexagonal Architecture and Domain-Driven Design.
python-gsc-specialist
Use when implementing new MCP tools, modifying auth/retry/quota logic, debugging Google API behavior, or refactoring gsc-mcp modules. Examples: "add a new GSC tool for keyword cannibalization", "fix quota tracker behavior", "update GA4 dimension filter logic for country+hostname". Do NOT use for writing tests (use…