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/davidyichengwei/agency/codex-collaborationnpx skills add davidYichengWei/Agency --skill codex-collaborationgit clone --depth 1 https://github.com/davidYichengWei/AgencyWrote 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/davidyichengwei/agency/codex-collaboration)<a href="https://agentmods.dev/skills/davidyichengwei/agency/codex-collaboration"><img src="https://agentmods.dev/badge/skills/davidyichengwei/agency/codex-collaboration.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.00048 | $0.01128 |
| Opus 5 | $0.00024 | $0.00564 |
| Sonnet 5 | $0.00010 | $0.00226 |
| Haiku 4.5 | $0.00005 | $0.00113 |
Grade A, and why
codex-collaboration 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 6d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Collaboration
Collaboration Modes
Review mode — Claude works, Codex reviews:
- Use for: code changes, final checks before gates
- Claude completes work → sends to Codex for review
- For code review: instruct Codex to use the
code-reviewskill - For designs/plans: Codex reviews directly (no subagent dispatch)
Parallel mode — both agents work independently, then compare:
- Use for: requirements drafting, design proposals, RCA investigation, complex problem-solving
- Claude and Codex both work the problem independently → compare results → synthesize
- Avoids anchoring bias — Codex isn't influenced by seeing Claude's approach first
Consensus Protocol
Consensus means Codex explicitly confirms it has no remaining concerns. Fixing issues and assuming consensus is NOT consensus — you must send your changes back to Codex and get explicit approval.
Review mode loop
- Codex reviews → provides findings
- You address the findings (fix code, update design, or argue why a finding is wrong)
- Resume the session and ask Codex to re-review your changes
- Codex confirms all issues resolved → consensus reached → proceed
- Codex raises new/remaining issues → go to step 2 (max 3 rounds)
- After 3 rounds with unresolved disagreements → escalate to user with both positions
Parallel mode loop
- Both work independently → compare results
- Identify agreements and disagreements
- For disagreements: each side argues with evidence → converge on a unified position
- If cannot converge (max 3 rounds) → escalate to user with both positions
The loop is not optional. Never skip re-review. Never declare consensus unilaterally. Codex must say it's satisfied.
Session Management
- New session: Start a fresh session for each task in
tasks.md, or when switching to a fundamentally different topic (e.g., from design review to code review). - Resume: Within the same task or topic, always resume the existing session. Codex retains full context — starting fresh loses valuable conversation history.
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.
- 6d ago First seen · 85 lines · 48 tokens per session scan A 2a5bbe8f018b
codex-collaboration is a skill published in the GitHub repository davidYichengWei/Agency (5 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 1,128 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…