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 briandconnelly/codex-in-claude --skill collaborating-with-codexgit clone --depth 1 https://github.com/briandconnelly/codex-in-claudeWrote 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/briandconnelly/codex-in-claude/collaborating-with-codex)<a href="https://agentmods.dev/skills/briandconnelly/codex-in-claude/collaborating-with-codex"><img src="https://agentmods.dev/badge/skills/briandconnelly/codex-in-claude/collaborating-with-codex/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/briandconnelly/codex-in-claude/collaborating-with-codex"><img src="https://agentmods.dev/badge/skills/briandconnelly/codex-in-claude/collaborating-with-codex.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.00141 | $0.03989 |
| Opus 5 | $0.00071 | $0.01995 |
| Sonnet 5 | $0.00028 | $0.00798 |
| Haiku 4.5 | $0.00014 | $0.00399 |
Grade A, and why
collaborating-with-codex scanned grade A with 1 finding 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 9d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
operations, `gh`, `curl`, or publishing inside it, because delegate runs have no network egress How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Collaborating with Codex
Use this skill as the router and shared safety contract for every Codex workflow. Retain responsibility for the work, and compose this guidance with applicable planning, debugging, review, and verification skills instead of replacing them.
Shared workflow
- Call
codex_statusbefore a paid call. Proceed only when bothready: trueandextra_args_valid: true. If either is false, stop and surface the corresponding readiness or operator-configuration detail. - Treat
rate_limitas advisory, with one exception.codex_statusreads it live from the Codex app-server (no model spend, nothing persisted), so it is current whenready: true. Decide spend from it: proceed onavailable; defer non-urgent calls onlimitedorexhausted; treatunknown(the live read failed, or it succeeded but reported no currently usable window —notesays which) orunavailable(this codex/account exposes no quota data) as uncertainty — neither permission nor denial. The account reports only the windows that currently bind it, soprimary(shorter/rolling) orsecondary(longer) may be null. Readnotefor plain-language caveats before relying on it. - Do not make a paid call when
rate_limit.statusisblocked. This is the exception to advisory: the backend reports a spend control (spend_control_reached: true) and the call will fail, so deferring does not help — no quota reset clears it. Stop and tell the user spending is administratively blocked on their Codex account. - Select one route below and load only its needed reference. Use a free dry-run when one exists, and read what it does not cover (see Data exposure).
- Declare the paid-call cap before the first active call, then stay within it.
- Branch on
ok, then on the concrete tool/result type. Verify claims before acting.
Route the request
| Situation | Tool or workflow | Read |
|---|---|---|
| One answer, design critique, or second opinion | codex_consult |
active workflows |
| Stuck mid-debugging or choosing between viable approaches | codex_consult |
active workflows |
| Review changes already represented in git | codex_review_changes |
active workflows |
| Proposed implementation diff from an isolated worktree | codex_delegate |
active workflows |
| A consult, review, or delegate that can exceed the synchronous deadline — high-reasoning-effort or broad repo-grounded work, a multi-file or whole-branch review, or a substantial implementation task | matching _async tool |
background jobs |
| Move the Claude session into a resumable Codex thread | codex_transfer |
session transfer |
| Claude and Codex attempt independently, then synthesize | independent two-member attempt | independent attempt |
| Claude drafts, Codex critiques, Claude revises | declared review–revise | review–revise |
| Optional parameters, idempotency, or a tool error | the tool already selected | options and errors |
| MCP server unavailable | limited read-only CLI fallback | server-down fallback |
| None of these, or a Codex call would not change the decision | no call — proceed without Codex | — |
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 228 lines · 141 tokens per session scan A e37133130950
collaborating-with-codex is a skill published in the GitHub repository briandconnelly/codex-in-claude (3 stars, last pushed 7d ago), licensed MIT. It adds 141 tokens to every session and 3,989 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
writing-release-notes
Use when preparing, refreshing, backfilling, or redrafting a release-notes page under docs/releases/ before opening a normal review pull request.
skills
Generate a complete SVG file from a natural language description using SEP-1577 multi-step sampling.
researching-references
Use when a change depends on how something outside this repository actually behaves — a markdown dialect, a file format, git, a protocol, a vendor API — and docs/design/reference/ has no current reference for it, or the one it has is past its review date. Researches from primary sources and writes a dated, versioned…
repository-protection
Use when changing branch or tag rulesets, required checks, or the bootstrap workflow: how repository protection is applied and kept in sync.
vault-workflow
Use when the user asks you to search, read, or reason about notes in their markdown vault — guides when to use which vault tool and how to chain them for good results.
pr-alignment-loop
Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…