/ 目錄 / 演練場 / Oh My OpenAgent
← 全部伺服器 ↗ GitHub
● 社群 code-yeongyu ⚡ 即開即用

Oh My OpenAgent

作者 code-yeongyu · code-yeongyu/oh-my-openagent

Wire Claude, Codex, and Gemini into one workflow — Oh My OpenAgent routes tasks to the best model and presents one surface.

Skill + harness that orchestrates multiple coding agents. Routes by task type, blends outputs, and keeps a shared task log. Useful when you don't want to be loyal to one vendor.

▶ 觀看演示 📦 安裝 💡 使用場景

為什麼要用

核心特性

即時演示

實際使用效果

就緒

安裝

作者儲存庫 · Claude Skills 官方文件

使用場景

實戰用法： Oh My OpenAgent

Ship a feature using the best of three models

👤 Claude Code users ⏱ ~15 min intermediate

何時使用： Claude is best at planning, Codex at refactors, Gemini at long-context — use them together.

步驟
  1. Plan
    Claude scopes.✓ 已複製
    → Plan ready
  2. Refactor
    Codex does the move.✓ 已複製
    → Code shipped
  3. Long context
    Gemini reviews full repo.✓ 已複製
    → Risks surfaced

結果： Each step uses the right tool.

組合

與其他 MCP 搭配，撬動十倍槓桿

oh-my-openagent-skill + gemini-cli-mcp

Plug Gemini CLI in as the long-context agent

Combine oh-my-openagent-skill with gemini-cli-mcp: Plug Gemini CLI in as the long-context agent✓ 已複製

工具

此 MCP 暴露的能力

工具輸入參數何時呼叫成本
route (see docs) Dispatch a task to a specific agent 1 call

成本與限制

運行它的成本

API 配額
Per provider
每次呼叫 Token 數
High — multiple LLMs
費用
Free skill; provider costs
提示
Pick two of three for most flows; three is overkill

安全

權限、密鑰、影響範圍

最小權限： multi-provider keys
憑證儲存： Keys per provider
資料出站： Configured providers

故障排查

常見錯誤與修復

Routing picks wrong agent

Override per-task; the heuristics are early

替代方案

Oh My OpenAgent 對比其他方案

替代方案何時用它替代權衡
Sticking with one agentSimplicityPer-task quality ceiling

更多

資源

📖 閱讀 GitHub 上的官方 README

🐙 查看未解決的 issue

🔍 瀏覽全部 400+ MCP 伺服器和 Skills