codex-delegation
Skill4 starsChanged 4 months agoMITView on GitHub
Use the local codex-agent-delegator MCP server to hand bounded, mechanical coding work to an installed agent while keeping architecture and review in the current Codex task. Do not delegate secrets, authentication/payment/cryptography changes, irreversible data migrations, major architecture decisions, or a task the user explicitly asked the current agent to implement personally. Before delegating, define: Use permissionMode: "workspace-write" and useWorktree: true for edits. Do not set full-access or allowUnsafe unless the user has authorized the specific risk. A custom backend always…
- Reads credentials
3 other projects use a version of this.
Adopted by
Most recently taken up by
- aikazu/claude-codex-mcptheir own version, first seen Nov 8, 2026
- agentstation/skillstheir own version, first seen Nov 1, 2026
- salalaslam/skillstheir own version, first seen Oct 20, 2026
Other versions3 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 3
- agentstation/skills★ 1same name
- aikazu/claude-codex-mcp★ 0same name
- salalaslam/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 repository2 other files it gives its agents.
- agy-workerSkill
- codex-reviewSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 1 is distinctive, and 8 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 5
Use the local codex-agent-delegator MCP server to hand bounded, mechanical coding work to an installed agent while keeping architecture and …
- Very specific: line 17
Do not delegate secrets, authentication/payment/cryptography changes, irreversible data migrations, major architecture decisions, or a task …
- Very specific: line 31
Use permissionMode: "workspace-write" and useWorktree: true for edits.
- Very specific: line 32
Do not set full-access or allowUnsafe unless the user has authorized the specific risk.
- Very specific: line 37
Call list_agent_backends if backend availability is unknown.
- Very specific: line 38
Call delegate_to_agent with a narrow task card.
- Distinctive: line 41
Follow the review skill. Fetch logs or patches only when the compact report does not provide enough evidence.
- Very specific: line 43
Call apply_agent_run only after review and with confirm: true.
- Very specific: line 44
Call cleanup_agent_run when the run and worktree are no longer needed.
“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
Agent Delegation Skill
Purpose
Use the local codex-agent-delegator MCP server to hand bounded, mechanical
coding work to an installed agent while keeping architecture and review in the
current Codex task.
Good delegation candidates
- mechanical refactors and API migrations;
- focused unit-test additions;
- documentation updates;
- repetitive style or UI changes;
- repository searches that benefit from a persisted report.
Do not delegate secrets, authentication/payment/cryptography changes, irreversible data migrations, major architecture decisions, or a task the user explicitly asked the current agent to implement personally.
Required task card
Before delegating, define:
- the exact expected outcome;
- narrow
allowedFilesand appropriateforbiddenFiles; - acceptance commands in
testCommands; - the backend:
agy,codex, orclaude; - the least privilege needed.
Use permissionMode: "workspace-write" and useWorktree: true for edits.
Do not set full-access or allowUnsafe unless the user has authorized the
specific risk. A custom backend always requires that explicit trust decision.
Workflow
- Call
list_agent_backendsif backend availability is unknown. - Call
delegate_to_agentwith a narrow task card. - For the default asynchronous mode, poll
get_agent_run_reportusing the returnedrunId. - Follow the review skill. Fetch logs or patches only when the compact report does not provide enough evidence.
- Call
apply_agent_runonly after review and withconfirm: true. - Call
cleanup_agent_runwhen the run and worktree are no longer needed.
Example
{
"repoPath": "/workspace/my-app",
"task": "Convert model interfaces to exported type aliases without changing runtime code.",
"agent": "codex",
"allowedFiles": ["src/models/*.ts"],
"forbiddenFiles": ["src/models/legacy/**", ".env"],
"testCommands": ["npm run typecheck"],
"permissionMode": "workspace-write",
"useWorktree": true
}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.

