use-coding-agents skill
✓ VerifiedUses installed coding agent CLIs as interchangeable, headless sub-agents within orchestrated workflows.
- GitHub stars
- 28
- Files
- 2
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the use-coding-agents skill do?
use-coding-agents uses installed coding agent CLIs as interchangeable, headless sub-agents within orchestrated workflows.
Summary generated from the skill's SKILL.md.
About the use-coding-agents skill
Developers building complex orchestration loops can use this skill to treat installed coding agent CLIs as interchangeable, headless workers. Instead of relying on the built-in orchestration features of specific tools like droid mission or hermes delegation, this skill strips them down to a simple contract: one prompt in, one result out. This allows a central orchestrator to manage multiple agents simultaneously, deciding which worker to launch based on availability or cost.
The skill supports a variety of agents including claude, codex, droid, grok, opencode, and pi. It manages the execution of these tools by passing prompts and capturing machine-readable results, often via JSON formats. To ensure safety and prevent file conflicts, it encourages the use of worktrees or specific directory isolation for each worker. It is designed for use within larger orchestration frameworks like dark-factory or bughunt to fan out tasks across a fleet of specialized coding agents.
What an agent can do with it
- 1Fan out coding tasksDistribute multiple independent coding units to different agents simultaneously to speed up development.
- 2Execute headless agent runsRun a coding agent without interactive prompts by using auto-approve flags for a streamlined workflow.
- 3Resume interrupted agent workContinue a previously blocked agent task by providing the missing information instead of starting from scratch.
- 4Optimize agent costsLaunch smaller, cheaper model variants of agents for simple tasks to save on token usage.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the use-coding-agents skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the use-coding-agents skill in Claude Code
~/.claude/skills/use-coding-agents/SKILL.md
$ npx degit av/skills/use-coding-agents ~/.claude/skills/use-coding-agentsInstall the use-coding-agents skill in Claude Code (project)
.claude/skills/use-coding-agents/SKILL.md
$ npx degit av/skills/use-coding-agents .claude/skills/use-coding-agentsInstall the use-coding-agents skill in Codex
~/.agents/skills/use-coding-agents/SKILL.md
$ npx degit av/skills/use-coding-agents ~/.agents/skills/use-coding-agentsInstall the use-coding-agents skill in Gemini CLI
~/.gemini/skills/use-coding-agents/SKILL.md
$ npx degit av/skills/use-coding-agents ~/.gemini/skills/use-coding-agentsInstall the use-coding-agents skill in Claude.ai
npx degit av/skills/use-coding-agents use-coding-agents && zip -r use-coding-agents.zip use-coding-agents # claude.ai → Customize → Skills → + → Create skill → Upload a skill → use-coding-agents.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachableav/skills/use-coding-agents is public and reachablegithub.com/av/skills/tree/HEAD/use-coding-agents ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/av/skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/av/skills/blob/HEAD/use-coding-agents/SKILL.md ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/av/skills/blob/HEAD/use-coding-agents/SKILL.md ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 178 linesgithub.com/av/skills/blob/HEAD/use-coding-agents/SKILL.md ↗Pass
SKILL.md
View on GitHubUse Coding Agents — Installed CLIs as Plain Sub-agents
Re-run <agent> --help before relying on any flag not listed here.
Principle
Every agent here is a worker: it receives a prompt, edits files in one directory, commits, prints a result, exits. Nothing more.
- Do not use the CLIs' own orchestration features. No
droid --mission, no codexmulti_agent, no hermesdelegate_task/moa/kanban, nogrok --agents, no opencode personas. Those are unvalidated here, spend tokens invisibly, and hide state from the orchestrator. - The orchestrator is the session running this skill (normally claude via the Agent tool or a orchestration skill). It plans units, writes prompts, launches workers, reads short results.
- Workers are interchangeable. Pick by availability and cost, not by feature.
Workers
| Agent | Invocation | Auto-approve | Status 2026-09-04 |
|---|---|---|---|
| claude | claude -p "<prompt>" |
--dangerously-skip-permissions |
PASS |
| codex | codex exec "<prompt>" (or prompt on stdin) |
--dangerously-bypass-approvals-and-sandbox |
PASS |
| droid | droid exec "<prompt>" |
--skip-permissions-unsafe (not with --auto) |
PASS |
| grok | grok -p "<prompt>" |
--always-approve |
PASS |
| grokc | COLORTERM=truecolor grokc -p "<prompt>" |
built in (podman, $PWD only) |
PASS |
| opencode | opencode run "<prompt>" |
--auto (without it a permission prompt hangs a headless run) |
PASS (default model now openrouter/~anthropic/claude-sonnet-latest) |
| pi | pi -p "<prompt>" |
none needed | PASS, local model, slow |
| hermes | hermes -z "<prompt>" --in <dir> |
--yolo |
FLAKY: write_file fails (DaemonThreadPoolExecutor ... _initializer); 1262 commits behind |
| copilot | copilot -p "<prompt>" -s |
--allow-all |
FAIL: no auth; needs interactive /login |
Facts from --help: grok 1.0.13 has no --check / --best-of-n; droid rejects --auto together
with --skip-permissions-unsafe; hermes restores the previous session's cwd unless --in is given.
Getting the result back
| Agent | Machine-readable result |
|---|---|
| claude | --output-format json (with -p) |
| codex | -o <file> writes the last message; --json for JSONL events |
| droid | -o json |
| grok | --output-format json, or --json-schema '<schema>' |
| opencode | --format json |
| pi | --mode json |
Simplest contract, works everywhere: tell the worker to write its output to a file and print one
line DONE|BLOCKED|FAILED <reason>. Read the file, not the transcript.
Cheaper / capped variants (validated)
Use when a unit is small. Same worker, fewer tokens:
- claude:
--model haiku --max-turns N(do not add--bareor--setting-sources ""; both drop auth) - codex:
-c model_reasoning_effort=low(minimalis rejected) - droid:
-r low -m claude-haiku-4-5-20251001 - grok:
--max-turns N --no-subagents --disable-web-search - opencode:
--variant minimal - pi:
--thinking off
Listing and picking models
Validated 2026-09-04. Pass the id with the agent's model flag (--model / -m).
| Agent | List available models | Default today | Flag |
|---|---|---|---|
| claude | no list command; aliases fable, opus, sonnet, haiku or a full id like claude-fable-5-1 |
account default | --model |
| codex | codex debug models (JSON catalog, 9 entries: gpt-5.6-sol/terra/luna, gpt-5.5, gpt-5.4, gpt-5.4-mini, gpt-5.3-codex-spark, …) |
gpt-5.6-sol (~/.codex/config.toml) |
-m |
| droid | no list command; /model in the TUI. Custom/local models are the customModels entries in ~/.factory/settings.json (ollama qwen3, glm-4.7-flash, kimi-k2.7-code, …) |
gpt-5.6-sol |
-m |
| grok | grok models (7 entries, grok-4.6 default, grok-4.5, …) |
grok-4.6 |
-m |
| opencode | opencode models (379 entries as provider/model; openrouter/~anthropic/... ids need the tilde) |
openrouter/~anthropic/claude-sonnet-latest (control/config/opencode.jsonc) |
-m |
| pi | pi --list-models [search] (table with context/max-out/thinking columns) |
harbor-llamacpp Qwen3-Coder-Next Q8 (~/.pi/agent/settings.json) |
--model |
| hermes | hermes model (interactive picker; --refresh re-fetches each provider's /v1/models); hermes config get model prints the default |
deepseek/deepseek-v4-flash-0731 via nous |
-m |
| copilot | no list command; /model in the TUI |
account default | --model |
Isolation
Two workers must never write the same file in the same tree. Use a worktree per worker:
claude -w <name>, droid -w <name>, grok -w <name>, hermes --worktree; for codex, opencode,
copilot, pi run git worktree add first and cd into it. (Worktree flags checked in --help only.)
Resume instead of restart
claude --resume <id>, codex exec resume --last, droid exec -s <id>, grok -r <id>,
hermes --resume <s>, opencode run -s <id>, copilot --continue, pi -c. Resume a BLOCKED
worker with the missing fact rather than re-dispatching cold.
Fan-out pattern
d=$(mktemp -d /tmp/orch-<slug>-XXXX)
cat > "$d/preamble.md" <<'P'
You are working on <project> at <code_path>.
Read CLAUDE.md / AGENTS.md / README.md first if present.
Commit with clear messages when done. Do not ask questions.
Do not start or reinstall opencode.service; the OpenCode daemon is retired.
Write your result to <unit_file> and print ONLY one line: DONE|BLOCKED|FAILED <reason>.
Before DONE, compare your diff and the observed result with the unit's Acceptance. If only a
proxy passed (tests, a build, a plan) or a gate is still open, print BLOCKED and name what is unmet.
After a tool error, do the next step it names before calling that tool again (table in
~/.agents/skills/use-coding-agents/SKILL.md, "Error → next step"). Never resend the same failing call.
P
cat > "$d/unit-1.md" <<'U'
Task: <what to do>
Acceptance:
- Deliver: <artifact or path>
- Scope: may change <paths>; must not touch <paths>
- Proof: <command or observation in the target environment>, not a proxy
- Gates: <checks and approvals to wait for; stop at a withheld one>
- Report: <format>
U
cd <code_path>
mkdir -p $d/cache-{1..5} # one writable cache per worker; a shared /tmp cache breaks gh
XDG_CACHE_HOME=$d/cache-1 claude -p "$(cat $d/preamble.md $d/unit-1.md)" --dangerously-skip-permissions > $d/1.log 2>&1 &
XDG_CACHE_HOME=$d/cache-2 codex exec --dangerously-bypass-approvals-and-sandbox < <(cat $d/preamble.md $d/unit-2.md) > $d/2.log 2>&1 &
XDG_CACHE_HOME=$d/cache-3 droid exec --skip-permissions-unsafe -f <(cat $d/preamble.md $d/unit-3.md) > $d/3.log 2>&1 &
XDG_CACHE_HOME=$d/cache-4 grok -p "$(cat $d/preamble.md $d/unit-4.md)" --always-approve -w unit-4 > $d/4.log 2>&1 &
XDG_CACHE_HOME=$d/cache-5 opencode run "$(cat $d/preamble.md $d/unit-5.md)" --auto > $d/5.log 2>&1 &
wait; tail -n1 $d/*.log
Prompts live on disk and are dispatched by path. The orchestrator authors nothing itself
(same discipline as timeboxed-iterating).
Acceptance contract
Every unit prompt carries the Acceptance: block above, filled in. A unit without it is not
ready to dispatch. Read a DONE against the same block, not against the worker's summary.
When the user corrects a result, rewrite the unit's Acceptance: from the correction before
resuming or re-dispatching; the worker's first line restates what changed and what will prove it.
Error → next step
Repeat calls after an error that already said why were the main avoidable cost in long runs.
| Error | Next step, before calling the tool again |
|---|---|
Claude Edit: file has not been read |
Read that exact path (a shell cat does not count), then Edit |
Edit: old string not found |
re-read that region, copy the exact text |
Claude Bash rejects sleep N; <status> |
Monitor with an until loop, or run_in_background |
| droid Bash times out at 60 s | keep every wait under 60 s; poll in steps |
command not found (e.g. dstask) |
command -v <tool> once; absent → switch tools (Backlog.md for tasks) |
gh: cache permission denied |
export XDG_CACHE_HOME=$(mktemp -d /tmp/cache-XXXX), retry once |
| guessed path does not exist | one rg --files | rg <name>, then use what it finds |
| skill path does not exist | skills live at ~/.agents/skills/<name>/SKILL.md; ls ~/.agents/skills once |
Rules
- Plain workers only. If you reach for a CLI's mission / delegation / persona feature, stop and fan out from the orchestrator instead.
- One unit, one directory, one commit per worker. Merge worktrees afterwards.
- Logs under
/tmpor the scratchpad, never in the repo. - Cap loops with
--max-turnswhere it exists, otherwise a turn budget in the prompt. - Bypass flags only in a worktree, in
grokc, or in a repo you cangit reset. - Backlog.md stays human. Workers do not touch
backlog/tasks/. - Smoke tests are one word. Validate a recipe with "Reply with the single word OK." only.
- Shared machines: your home only. Never read or change another user's sessions, worktrees, agent configs or keys. Shared installs are an admin task.
- Do not invent flags. Not in this file → run
--helpand paste the real one.
Related skills
overnight— dispatch approved work items to these workers in the backgroundtimeboxed-iterating,workgraph,workmachine,gauntlet,dark-factory,bughunt— orchestration loops that use these workers
Files in this skill
2use-coding-agents skill questions
How do I install the use-coding-agents skill in Claude Code?
Run npx degit av/skills/use-coding-agents ~/.claude/skills/use-coding-agents. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the use-coding-agents skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How should I use the coding agent CLIs in a workflow?
Use them as plain workers with a single headless invocation: one prompt in and one result out, deliberately ignoring their built-in orchestration features.
How can I ensure workers do not interfere with each other?
Each worker should use a dedicated worktree or directory to ensure they never write to the same file in the same tree.
What is the best way to get machine-readable results from these agents?
The simplest contract is to instruct the worker to write its output to a file and print a single status line like DONE|BLOCKED|FAILED.