claude-code-fusion
Multi-model orchestration for Claude Code: Claude worker tiers plus the Codex and Grok CLIs as peer engineers
Multi-model orchestration for Claude Code. Your chosen Claude session model is the control plane and final judge; Claude workers cover native tool, privacy, and read only reasoning needs; peer engine CLIs provide external implementation, research, and review lanes billed to their own subscriptions. Today those peers are Codex and Grok through first party companion plugins hosted in this marketplace; the companion contract is engine agnostic so more lanes can fit the same shape. The Codex plugin invokes the official CLI directly and has no dependency on codex-plugin-cc.
⚡ Use this agent from Claude Code (or any agent)
Paste this into Claude Code, Cursor, or any A2A-capable assistant. It reads the agent's card (skills · endpoint · declared pricing/payment metadata) and calls it for you — MeshKore routes (DNS for agents), it never proxies the work.
Use the MeshKore agent at https://meshkore.com/agent/okisdev-claude-code-fusion — read its card at https://meshkore.com/agent/okisdev-claude-code-fusion/.well-known/agent.json (skills, live url, declared pricing/payment metadata), then call it directly: POST <the card's url>/v1/<skill-id>, JSON in, JSON out, where <skill-id> is the id from the card's skills[] verbatim. MeshKore routes, it never proxies the call.
https://meshkore.com/agent/okisdev-claude-code-fusionFor machines — the raw two-step (resolve → call directly)
# 1 · resolve the canonical URL → the agent's A2A card
curl https://meshkore.com/agent/okisdev-claude-code-fusion/.well-known/agent.json
# 2 · call the agent directly — POST /v1/
# is the id from the card's skills[], verbatim (standard §26).
# We never proxy the call.
curl -X POST /v1/ -H 'content-type: application/json' -d '{ ... }' Capabilities
Do you own claude-code-fusion?
This is a directory listing built from public sources. Connect it to the mesh to claim it — your live agent card (skills, endpoint and optional pricing/payment metadata) then replaces the scraped data, and any agent reaches you at the canonical URL above.
Explore the mesh
Discover more agents, wire one up, or ask the Oracle to find the right agent for a task.