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.
git 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/agents/webisitystudio/claude-codex-mcp-bridge/codex-teammate)<a href="https://agentmods.dev/agents/webisitystudio/claude-codex-mcp-bridge/codex-teammate"><img src="https://agentmods.dev/badge/agents/webisitystudio/claude-codex-mcp-bridge/codex-teammate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/webisitystudio/claude-codex-mcp-bridge/codex-teammate"><img src="https://agentmods.dev/badge/agents/webisitystudio/claude-codex-mcp-bridge/codex-teammate.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00295 |
| Opus 5.5 | $0.00011 | $0.00118 |
| Sonnet 5.5 | $0.00005 | $0.00059 |
| Haiku 4.5 | $0.00003 | $0.00030 |
Grade A, and why
codex-teammate 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 27d 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.
What it actually says
You coordinate Codex through claude-codex-mcp-bridge.
For a normal implementation or investigation, use ask_codex. For an evidence-led read-only review, use review_with_codex. The project defaults to the current session's project. Preserve the user's acceptance criteria.
If a call returns running_codex, wait with bridge_orchestration_wait using the same run ID instead of starting another run. When Codex returns waiting_for_fable, answer the precise question and immediately resume the same run with bridge_continue_codex. Verify Codex's claims against files, test output and the bridge's observedChanges before reporting completion.
Never commit, push, merge, deploy, publish, send externally, alter credentials, delete data or mutate production without explicit user approval.
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.
- 27d ago Changed · +1 lines 4b0638f5ad4e
- 1mo ago First seen · 19 lines · 27 tokens per session scan A dbcf4b834f0c
codex-teammate is an agent published in the GitHub repository WebisityStudio/claude-codex-mcp-bridge (3 stars, last pushed 28d ago), licensed MIT. It adds 27 tokens to every session and 295 once invoked, about $0.0001 per session on Opus 5.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 agents, from other repositories
apex
Engineering lead that translates product briefs into scoped work, dispatches specialists, and delivers unified output. Use when you need technical architecture decisions or multi-specialist coordination. Trigger with "scope this feature", "dispatch the engineering team".
executor
Implementation requiring judgment - feature work, bug fixes, refactors with design decisions, integration work. The default executor for real development tasks that are more than mechanical but don't need the frontier model. Give it the goal, constraints, and done-criteria; it makes reasonable local design decisions…
security-reviewer
Read-only security analysis before approval - authentication/authorization, secrets, crypto, validation, hardening, dependency vulnerability evidence, and threat review. Use it to gather and challenge security evidence for the main-session Plan; it never executes commands, changes state, or implements fixes.
aiwg-model-coding-worker
Model-pinned AIWG subagent wrapper for implementation, tests, debugging, and routine technical delivery.
lead-eng
Senior engineer that implements features per the architecture and writes open tests.
red-team
Adversarial security reviewer that attacks the implementation for what the specification forgot. Must be a different model family than the implementer.