.agents/skills/codex-worker/SKILL.md
Spawn and manage multiple Codex CLI agents via tmux to work on tasks in parallel. Use whenever a task can be decomposed into independent subtasks (e.g. batch triage, parallel fixes, multi-file refactors). When codex and tmux are available, prefer this over the built-in Task tool for parallelism.
npx skillsauth add moonshotai/kimi-cli codex-workerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Orchestrate multiple Codex CLI (codex) agents running in parallel, each in its
own git worktree and tmux session.
When to use: Whenever you identify that a task can be split into independent subtasks — don't wait for the user to ask for parallelism. Examples:
Replaces Task tool: When codex and tmux are available in the
environment, use codex workers instead of the built-in Task (subagent) tool.
Codex workers are full-featured agents with their own file system access, shell,
and isolated worktree — far more capable than subagents.
command -v codex && codex login status && command -v tmux
All three must succeed. The project must be a git repository.
Git branch and worktree directory share a task name:
<type>-<issue number (optional)>-<short description>
The tmux session adds a codex-worker- prefix so workers are easy to filter:
| | Format | Example |
|---|---|---|
| Task name | <type>-<number>-<desc> | issue-836-prompt-dollar-sign |
| Git branch | same as task name | issue-836-prompt-dollar-sign |
| Worktree dir | <project>.worktrees/<task> | kimi-cli.worktrees/issue-836-prompt-dollar-sign |
| tmux session | codex-worker-<task> | codex-worker-issue-836-prompt-dollar-sign |
More examples:
issue-518-mcp-config-isolationfix-share-dir-skills-pathfeat-ask-user-toolrefactor-jinja-templatesList only codex workers: tmux ls | grep ^codex-worker-
Prefer tmux + interactive codex for all tasks. It supports multi-turn dialogue,
the user can tmux attach to inspect or intervene, and you can send follow-up
prompts from outside.
NAME="issue-836-prompt-dollar-sign" # task name
SESSION="codex-worker-$NAME" # tmux session name
PROJECT_DIR="$(pwd)"
WORKTREE_DIR="$PROJECT_DIR.worktrees"
# 1. Create worktree (skip if exists)
git worktree add "$WORKTREE_DIR/$NAME" -b "$NAME" main 2>/dev/null
# 2. Launch interactive codex inside tmux
tmux new-session -d -s "$SESSION" -x 200 -y 50 \
"cd $WORKTREE_DIR/$NAME && codex --dangerously-bypass-approvals-and-sandbox"
The Codex TUI needs time to initialize before it accepts input.
After launching a session, wait at least 5 seconds before sending
a prompt. Then send the text followed by Enter. If the prompt stays
in the input field without being submitted, send an additional Enter.
sleep 5 # wait for Codex TUI to initialize
tmux send-keys -t "$SESSION" "Your prompt here" Enter
# If it doesn't submit, send another Enter:
# tmux send-keys -t "$SESSION" Enter
tmux capture-pane -t "$SESSION" -p | tail -30
tmux attach -t "$SESSION"
TASKS=(
"issue-518-mcp-config-isolation|Triage #518: MCP config 被子 agent 继承的隔离问题。分析根因,给出修复方案。"
"issue-836-prompt-dollar-sign|Triage #836: prompt 包含 $ 时启动静默失败。分析根因,给出修复方案。"
)
PROJECT_DIR="$(pwd)"
WORKTREE_DIR="$PROJECT_DIR.worktrees"
for entry in "${TASKS[@]}"; do
NAME="${entry%%|*}"
PROMPT="${entry#*|}"
SESSION="codex-worker-$NAME"
git worktree add "$WORKTREE_DIR/$NAME" -b "$NAME" main 2>/dev/null
tmux new-session -d -s "$SESSION" -x 200 -y 50 \
"cd $WORKTREE_DIR/$NAME && codex --dangerously-bypass-approvals-and-sandbox"
sleep 5 # wait for Codex TUI to fully initialize
tmux send-keys -t "$SESSION" "$PROMPT" Enter
done
codex execOnly use codex exec when you explicitly don't need follow-up (e.g. CI, pure
analysis with -o output). It does not support multi-turn dialogue.
codex exec --dangerously-bypass-approvals-and-sandbox \
-o "/tmp/$NAME-result.md" \
"Your prompt here"
List active workers:
tmux ls | grep ^codex-worker-
Kill a finished worker:
tmux kill-session -t "codex-worker-$NAME"
Clean up worktree after merging:
tmux kill-session -t "codex-worker-$NAME" 2>/dev/null
git worktree remove "$WORKTREE_DIR/$NAME"
git branch -d "$NAME"
Batch cleanup of dead sessions:
tmux list-sessions -F '#{session_name}:#{pane_dead}' \
| grep ':1$' \
| cut -d: -f1 \
| xargs -I{} tmux kill-session -t {}
tools
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Kimi's capabilities with specialized knowledge, workflows, or tool integrations.
tools
Answer Kimi Code CLI usage, configuration, and troubleshooting questions. Use when user asks about Kimi Code CLI installation, setup, configuration, slash commands, keyboard shortcuts, MCP integration, providers, environment variables, how something works internally, or any questions about Kimi Code CLI itself.
tools
Sample plugin demonstrating the Skills + Tools model. Includes a Python tool (greeting) and a TypeScript tool (calculator).
testing
Audit all git worktrees in the current project. Use when the user asks about worktree status, which branches are merged, which have uncommitted changes, or which worktrees can be safely cleaned up.