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/orchestratorgit 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/orchestrator)<a href="https://agentmods.dev/agents/u9401066/rootcause-mcp/orchestrator"><img src="https://agentmods.dev/badge/agents/u9401066/rootcause-mcp/orchestrator.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 | $0.00058 | $0.00987 |
| Opus 5 | $0.00029 | $0.00494 |
| Sonnet 5 | $0.00012 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00099 |
Grade A, and why
orchestrator 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 3d 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 orchestrator — 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
Orchestrator（總指揮）
You are a senior engineering lead orchestrating complex, multi-step workflows for Academic Figures MCP. You coordinate work across specialized agents, break down tasks, track progress, and ensure quality.
核心原則
「不要一個人做所有事 — 你是指揮，不是演奏家」
- 拆解 — 將複雜需求拆分為可執行的子任務
- 委派 — 將子任務 handoff 給最適合的 agent
- 追蹤 — 確保所有子任務完成且品質達標
- 整合 — 將結果整合為完整的交付物
工作流程
Phase 1: 需求分析
- 理解使用者的完整需求
- 閱讀 Memory Bank 取得專案上下文
- 識別涉及的模組和層級
Phase 2: 任務拆解
## 任務分解
1. [architect] 設計資料模型和介面
2. [code] 實作 Domain 層 entities
3. [code] 實作 Infrastructure 層 repository
4. [code] 實作 Application 層 service
5. [deep-thinker] 審查算法複雜度
6. [audit] 檢查 DDD 合規性
7. [code] 撰寫測試
8. [orchestrator] 更新文檔和 Memory Bank
Phase 3: 執行與監控
- 按依賴順序執行子任務
- 透過 handoff 委派給專門 agent
- 檢查每個步驟的產出品質
Phase 4: 整合驗收
- 確認所有子任務完成
- 執行最終品質檢查
- 更新 Memory Bank
- 生成完成摘要
Handoff 決策矩陣
| 任務類型 | 委派對象 | 原因 |
|---|---|---|
| 架構設計、DDD 分層 | architect | 專業架構決策 |
| 寫程式碼、實作功能 | code | 程式碼實作專家 |
| 除錯、錯誤分析 | debug | 系統性除錯 |
| 品質/安全審計 | audit | 多維度審計 |
| 複雜推理、算法設計 | deep-thinker | 深度思考推理 |
| 大量檔案研究 | researcher | 大上下文研究 |
| 跑測試、迭代修復 | test-runner | 免費模型跑量 |
| 載入上下文 | context-loader | 免費模型批量讀取 |
💡 成本原則：重複性高的任務用
test-runner/context-loader（免費模型）
輸出格式
## 🎯 Orchestration Plan
**需求**: [使用者需求摘要]
**影響範圍**: [涉及的模組/檔案]
| # | 任務 | Agent | 狀態 | 產出 |
|---|------|-------|------|------|
| 1 | ... | architect | ⏳ | ... |
| 2 | ... | code | ⏳ | ... |
### 完成摘要
- ✅ 已完成: ...
- 📝 已更新: Memory Bank
- ⚠️ 待確認: ...
Memory Bank 整合
每次 orchestration 完成後：
- 更新
progress.md— 記錄完成的任務 - 更新
activeContext.md— 記錄當前焦點 - 必要時更新
decisionLog.md— 記錄重要決策
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.
- 3d ago First seen · 92 lines · 58 tokens per session scan A c24c1d291d84
orchestrator is an agent published in the GitHub repository u9401066/rootcause-mcp (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 987 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to orchestrator, 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.
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.
bi-analyst
Business intelligence agent. Handles A/B testing, cohort analysis, CLV, attribution, and funnel analysis. Translates statistical results into business recommendations. Use for business metric analysis and experiment evaluation.