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 agentmods add skills/arystos/skill-codex/codex-bridgenpx skills add Arystos/skill-codex --skill codex-bridgegit clone --depth 1 https://github.com/Arystos/skill-codexWhat 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 | $0.00176 | $0.03051 |
| Opus 5 | $0.00088 | $0.01525 |
| Sonnet 5 | $0.00035 | $0.00610 |
| Haiku 4.5 | $0.00018 | $0.00305 |
Grade A, and why
codex-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 2d 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Bridge
This skill turns OpenAI Codex into a peer engineer you can delegate bounded implementation work to, and a second reviewer you can call for independent code review or technical consultation. It uses the codex_exec MCP tool provided by the skill-codex MCP server.
When to use this skill
Load this skill automatically when the user's request matches any of the following patterns:
Delegation triggers (use delegate workflow below):
- "implement X" / "write a function that X" / "create a script that X"
- "generate tests for X" / "add unit tests" / "scaffold tests"
- "port X to Y" / "convert X to Y" / "rewrite X in Y"
- "refactor this file" (single-file, clear target)
- "write a migration" / "create boilerplate for X"
- Any bounded, single-file or small multi-file code task with a clear spec
Review triggers (use review workflow below):
- "review my changes" / "review this diff" / "code review"
- "second opinion on this code" / "independent review"
- "check this for bugs" / "audit this for security issues"
- Before committing critical code (auth, payments, crypto, concurrency)
Consult triggers (use consult workflow below):
- "what do you think about this approach"
- "is this the right way to do X"
- "second opinion on my plan"
- Debugging when Claude has failed 3+ times on the same issue
When NOT to use this skill
Skip Codex and do the work yourself when:
- Task is <50 lines and faster to do directly
- Task requires deep conversation context Codex won't have
- Cross-module architectural refactor
- Ambiguous requirements needing user clarification
- Planning, brainstorming, or design decisions (Claude handles these)
- User explicitly asks you to do the work yourself
Workflows
Workflow 1: Delegate implementation (delegate)
Use when the user asks for a bounded implementation task with a clear spec.
Steps:
- Verify the task is well-scoped. If the request is vague, ask one clarifying question before delegating. A good delegation prompt has: exact file paths, specific change required, constraints (language, style, naming), and a clear "done" condition.
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.
- 2d ago First seen · 218 lines · 176 tokens per session scan A 54e085e29446
codex-bridge is a skill published in the GitHub repository Arystos/skill-codex (5 stars, last pushed 1mo ago), licensed MIT. It adds 176 tokens to every session and 3,051 once invoked, about $0.0009 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
extension-creator
Create, scaffold, customize, validate, and locally test Qwen Code extensions. Use when the user wants a new Qwen Code extension, needs help choosing an extension template, wants to add QWEN.md context, commands, skills, agents, MCP servers, settings, hooks, channels, or LSP servers, or asks how to link and test an…
dispatching-parallel-agents
当面对 2 个以上可以独立进行、无共享状态或顺序依赖的任务时使用.
memory-management
Guide the agent to recall, remember, and route durable learning into Memory, Skills, Scheduled Tasks, or Tape.
rulesync
Generates and syncs AI rule configuration files (.cursorrules, CLAUDE.md, copilot-instructions.md) across 20+ coding tools from a single source. Use when syncing AI rules, running rulesync commands, importing or generating rule files, or managing shared AI coding configurations.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.