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 Cyruskraad/codex-claude-mcp --skill claude-code-bridgegit clone --depth 1 https://github.com/Cyruskraad/codex-claude-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/skills/cyruskraad/codex-claude-mcp/claude-code-bridge)<a href="https://agentmods.dev/skills/cyruskraad/codex-claude-mcp/claude-code-bridge"><img src="https://agentmods.dev/badge/skills/cyruskraad/codex-claude-mcp/claude-code-bridge/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/skills/cyruskraad/codex-claude-mcp/claude-code-bridge"><img src="https://agentmods.dev/badge/skills/cyruskraad/codex-claude-mcp/claude-code-bridge.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.00032 | $0.00805 |
| Opus 5 | $0.00016 | $0.00402 |
| Sonnet 5 | $0.00006 | $0.00161 |
| Haiku 4.5 | $0.00003 | $0.00081 |
Grade A, and why
claude-code-bridge 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Bridge
Use this permission-aware local wrapper. Call claude_health({}) first; proceed only when CLI features and authentication are ready.
Start work
claude_task selects workspace, access, model, effort, turns, and session:
{
workspace: string, // absolute existing real path
prompt: string, // 1-100,000 characters
access?: "inspect" | "write", // default: inspect
model?: string, // health alias or full Claude model ID
effort?: "low" | "medium" | "high" | "xhigh" | "max",
max_turns?: number, // 1-100; default: 20
session?: // default: { mode: "new" }
| { mode: "new" }
| { mode: "resume"; session_id: string }
| { mode: "cloud_create"; description?: string }
| { mode: "cloud_attach"; target: string },
execution?: {
mode?: "auto" | "sync" | "async", // default: auto
wait_seconds?: number, // 0-45; default: 45
timeout_seconds?: number // 30-7200; default: 1800
}
}
- Default to
inspect. Usewriteonly for an explicitly authorized change in an absolute, existing, real Git worktree. It selects ClaudeacceptEdits, auto-approving file edits and Claude-classified common filesystem commands in the validated workspace; other commands and protected paths retain Claude permission checks. This is not OS confinement. Commits, pushes, network, and other external effects require separate target-scoped authorization; never infer a remote, branch, or account. - Match model/effort to task difficulty; leave them unset for Claude defaults.
- Use explicit session IDs/cloud targets; never infer “the most recent.”
cloud_createis schema-only and returnsunsupported-session-mode; create interactively in Claude Code, then use explicitcloud_attach.- Inspect uses bounded read/search and plan permissions. Chrome/nested MCP remain disabled; never request bypasses.
After inspect, authorized edits require a new write task; resume with the captured claude_session_id.
Manage jobs
claude_job_status:{ job_id }claude_job_result:{ job_id, cursor? }; follownext_cursoruntil absent. Each page is bounded.claude_job_continue:{ job_id, prompt, execution? }. It preserves the captured workspace, access, model, effort, maximum-turn ceiling, and explicit session. Never add escalation fields.claude_job_cancel:{ job_id }; cancel only queued or running work.claude_job_forget:{ job_id }; forget only terminal work. It deletes bridge metadata/output, not Claude's own transcript.
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.
- 8d ago First seen · 56 lines · 32 tokens per session scan A 336e084b4a46
claude-code-bridge is a skill published in the GitHub repository Cyruskraad/codex-claude-mcp (0 stars, last pushed 12d ago), licensed MIT. It adds 32 tokens to every session and 805 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…