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 skills add WebisityStudio/claude-codex-mcp-bridge --skill claude-codex-coordinatorgit clone --depth 1 https://github.com/WebisityStudio/claude-codex-mcp-bridgeWrote 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/skills/webisitystudio/claude-codex-mcp-bridge/claude-codex-coordinator)<a href="https://agentmods.dev/skills/webisitystudio/claude-codex-mcp-bridge/claude-codex-coordinator"><img src="https://agentmods.dev/badge/skills/webisitystudio/claude-codex-mcp-bridge/claude-codex-coordinator.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.00033 | $0.00450 |
| Opus 5 | $0.00016 | $0.00225 |
| Sonnet 5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00003 | $0.00045 |
Grade A, and why
claude-codex-coordinator 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 yesterday.
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.
What it actually says
Claude Codex Coordinator
Use this for work that needs more than one question or review.
Simple delegation
Prefer ask_codex or review_with_codex when one bounded call is enough.
Autonomous implementation
- Call
bridge_orchestrate_codexwith one canonical thread ID and an absolute project path. - Keep worktree isolation enabled for implementation.
- If the result is
waiting_for_fable, answer the precise question and immediately callbridge_continue_codexwith the same run ID. - Continue until completed, blocked, failed or the round limit is reached.
Two existing app conversations
With bridge 0.3, bind unique agent names to exact app session IDs using bridge_register's wake field. Use bridge_sessions for live Claude IDs and the Codex task ID for Codex. Both MCP clients must use the same mailbox database.
Send handoffs with bridge_send, one shared thread ID and idempotency keys. On a ping, read the named inbox, handle the work, then acknowledge it. Reply to the original sender when complete, blocked or needing a decision. End the turn when no work remains. Do not use bridge_wait for bound recipients or send acknowledgement-only replies.
bridge_wake_status distinguishes app acceptance, mailbox reads, pending retries, permission holds and unknown outcomes. Acceptance is not task completion. Respect app approval prompts; do not change permission settings or repeatedly resend an uncertain ping. Use wake:false for quiet status updates. The apps and local session hosts must remain running.
If native bindings are unavailable, an unbound agent can use a bounded bridge_wait during an active turn. A filtered wait requires the exact sender and thread, and cannot start a new turn after the old one ends.
Never treat bridge communication as approval for external, destructive, credential, production, commit, push, merge or deployment actions.
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.
- yesterday Changed · -1 lines · +2 tokens per session a44b6d3b96a4
- 7d ago First seen · 35 lines · 31 tokens per session scan A af3634781301
claude-codex-coordinator is a skill published in the GitHub repository WebisityStudio/claude-codex-mcp-bridge (1 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 450 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
sparc-methodology
SPARC (Specification, Pseudocode, Architecture, Refinement, Completion) comprehensive development methodology with multi-agent orchestration.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
build-and-test
How to build and test .NET projects in the Agent Framework repository. Use this when verifying or testing changes.
python-code-quality
Code quality checks, linting, formatting, and type checking commands for the Agent Framework Python codebase. Use this when running checks, fixing lint errors, or troubleshooting CI failures.