codex-collab
Skill1 starsChanged 59 days agoMITView on GitHub
Coordinate Claude Code reviews and Grok Build or DeepSeek Harness execution from Codex, with isolated worktrees, shared project memory, and verified handoffs. Use for cross-agent coding teamwork, task dispatch, or acceptance checks.
3 other projects use a version of this.
Adopted by
Most recently taken up by
- xzljq/claude-skillstheir own version, first seen Oct 13, 2026
- kohoj/skillstheir own version, first seen Apr 6, 2026
- Kevin7Qi/codex-collabtheir own version, first seen Feb 28, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- Kevin7Qi/codex-collab★ 99same name
- kohoj/skills★ 1same name
- xzljq/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repositoryOne other file it gives its agents.
- AGENTS.mdAGENTS.md
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Keep Codex as the controller.
- Distinctive: line 18
Read the user's project instructions.
- Very specific: line 19
Run worktree <absolute-repository> <unique-name>.
- Very specific: line 20
Write a JSON contract with id, role, cwd, objective, allowed_paths, acceptance, input_revision, and timeout_seconds.
- Very specific: line 21
Run dispatch <contract.json>, then inspect status <id>.
- Very specific: line 22
Read actual outputs and run acceptance checks.
- Distinctive: line 24
Use Chinese or English according to the user.
- Very specific: line 36
Read <repo>/docs/ARCHITECTURE.md for the state machine and <repo>/docs/CONTEXT_MEMORY.md for commands.
- Very specific: line 41
Start handoff at ceil(0.8 * min(256000, known-window)).
- Very specific: line 43
Do not claim control-plane registration is OS-enforced stopping, or that a local ack proves a model read the package.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Codex Collab
Keep Codex as the controller. Use Claude for independent review and Grok/DeepSeek Harness for bounded implementation tasks. Choose agents by task fit, availability, modality, and dependencies; do not require every agent for every request.
Locate the installation
This skill ships with a Python CLI. Resolve this SKILL.md through any symlink: its containing directory is <repo>/skill, and the installation root is <repo>. Run python3 <repo>/scripts/collab.py. If installed as a copied standalone file without the sibling CLI, explain that the full repository is required; do not guess a machine-specific path.
On first use, read <repo>/README.md and <repo>/docs/INSTALL.md, then run doctor and list. Doctor checks installation, not account availability. Do not install dependencies, change accounts, or launch paid workers beyond the user's task authorization.
Run a bounded task
- Read the user's project instructions. Define the goal, owner, allowed files, input commit, and concrete acceptance check.
- Run
worktree <absolute-repository> <unique-name>. Source inputs must be committed; do not silently omit dirty changes. Use the returned directory and full SHA. - Write a JSON contract with
id,role,cwd,objective,allowed_paths,acceptance,input_revision, andtimeout_seconds. Roles:claude-reviewer,grok-worker,dsh-worker. Use specific relative allowed paths, never the repository root. Unknown contract fields are rejected. - Run
dispatch <contract.json>, then inspectstatus <id>. Parallel tasks need isolated worktrees. A submitted task is not automatically resubmitted; recovery or retries must preserve the original record. - Read actual outputs and run acceptance checks.
deliveredis only a transport/scope milestone. Independently review meaningful changes, then callaccept <id> <nonempty-evidence-file>only after verification.
Use Chinese or English according to the user. Generate contracts yourself; do not require users to write orchestration JSON.
Models, review, and child agents
- DSH defaults to
tier=flash, formally mapped todeepseek-flashby the pinned project overlay.promaps todeepseek-v4-pro. Supported effort values areoff,high,max; choose proportionately. Verify actual availability instead of assuming a model name is current. - DSH defaults to the
standardpreset with native subagent tools. Explicitminimaldoes not have the same tool set. Nativedescribe_imageuses DeepSeek vision through a bridge; this is not direct image input in the coding conversation. - Claude supports contract
modelandthinking. Grok uses its isolated native model/effort settings; the adapter rejects unsupported shortcuts.grok modelscan fail to refresh while showing cached entries—report that distinction. - Each parent may use native child agents within the user's authorization. Inherit file boundaries and memory, avoid overlapping writes, choose supported models/effort, wait for child results, and report unknown telemetry honestly. Preserve native recursion/concurrency protections.
- If Claude hits quota/authentication trouble, refresh the same account's persisted settings by rebuilding only the owned, already-finished CCB session; make at most one small health check. If still unavailable and the task permits reviewer substitution, use an independent GPT subagent. Record requested/actual reviewer, original task, failure reason, and model. Never label a controller self-review or GPT review as Claude's work.
Shared memory and handoffs
Read <repo>/docs/ARCHITECTURE.md for the state machine and <repo>/docs/CONTEXT_MEMORY.md for commands.
- Dispatch freezes the input commit's
docs/project-memory/TEAM.mdandPROJECT.mdwhen present.memory_pathsappends other reviewed files; it cannot remove default rules. Receipts and prompts carry the same SHA-256 snapshot. Uncommitted edits do not become shared truth. - Workers propose memory in allowed files. The controller verifies and accepts the task, then uses
memory-promoteto check the delivered digest and freshness. Review and commit the promoted file before using it in future snapshots. Never store credentials, full private conversations, or hidden reasoning in shared memory. - Register manageable sessions with
context register; bind contracts usingcontext_session_id. Use actual current/estimated pressure, not cumulative billing tokens. Unknown or stale readings stay unknown. A bounded manual override needs an explicit reason and a timeout of at most 600 seconds. - Start handoff at
ceil(0.8 * min(256000, known-window)). Parent and child sessions both inherit this rule. DSH pressure polling can request cancellation; arbitrary desktop and native child sessions are not universally auto-monitored. - Create a hashed
handoff-package, register a standby successor, andprepare. Verify native predecessor/child termination beforestop. Give the successor the immutable package plus the later stop certificate/evidence. Only after it actually reads and verifies them callack.abortmay undo a preparation before stop; it cannot revive a stopped owner. - Do not claim control-plane registration is OS-enforced stopping, or that a local
ackproves a model read the package. A fresh DSH job is a fresh native session; CCB can reuse panes, so new-context work should use a new isolated unit and verify identity.
Recover without inventing success
cancel is a request: confirm the native terminal state. unknown keeps the worktree occupied. If a runner disappeared, use reconcile, inspect the native job/trace, then resolve <id> delivered|failed|cancelled <evidence> --note <reason>. A late native completion still needs scope and output verification before acceptance.
Operate only this installation's worktrees, CCB namespaces, and DSH hub. Do not stop unrelated processes, modify global credentials, merge, push, publish, or message others unless the user's task authorizes it.
Shared project task skills
Contracts accept skills: ["lark-doc", "langfuse"]. Omission uses explicit domain keywords; skills: [] disables selection. skills list reports the registered installed catalog; skills check <names> freezes and validates the selected dependency closure. With no names, skills check checks entries individually. Missing sources fail explicitly; third-party skill content is not bundled with this repository.
At dispatch, freeze selected UTF-8 text resources and SHA-256 hashes; materialize them under the target workspace's .collab-skills/<task-id>/. Keep that directory outside allowed write paths. Read the bundled collab-tool-guide before selected tool skills and validate dependencies with the target Python interpreter. Credentials, CLI installations and MCP access are not shared automatically.
Parents pass the same package entrypoints, root and expected hash to native children. Inheritance is instruction-only, not universally intercepted or proven. This pool selects registered installed skills per project task; it does not discover arbitrary project-local skill folders. Read <repo>/docs/SHARED_SKILLS.md and <repo>/docs/TOOL_SKILLS.md for limits and checks. Default list/status omit snapshot bodies; --full exposes complete records.
Bounded recursive self-improvement
When the user authorizes improving this adapter, use it to dispatch isolated implementation, independent review, and successor validation. Fix each round's input SHA, owner, allowed paths, acceptance checks and stopping conditions. A review finding may start a new bounded repair task with a new ID; re-run verification against the resulting version. Stop when the authorized objective is met or a blocking condition requires user input.
Native children may assist within harness recursion/concurrency limits. Do not delegate this control plane recursively to workers, expand authorization, or run an unattended endless improvement loop. The controller reads actual changes, runs checks and records evidence before adopting an improved version. Preserve the previous revision and use a reviewed revert if validation fails. See <repo>/docs/SELF_IMPROVEMENT.md.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

