execution-orchestrator

A system for carrying out multi-step coding tasks by sending independent pieces to agents in parallel or in a required order. It collects their results, detects conflicts, and coordinates a final review.

In plain words
What is it for?
Use it after a task plan is made to dispatch agents, combine their work, handle conflicting changes, and request an integration review.
Why use it?
It helps manage tasks with dependencies or multiple work areas without losing the context each agent needs.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/d3x293/code-crew/execution-orchestrator
Any agent
npx skills add d3x293/code-crew --skill execution-orchestrator
Clone the repo
git clone --depth 1 https://github.com/d3x293/code-crew

Made for: Claude Code, Codex.

Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,253 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.02253
Opus 5 $0.00020 $0.01126
Sonnet 5 $0.00008 $0.00451
Haiku 4.5 $0.00004 $0.00225

Measured 2d ago against content hash 1df6a07f91f7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

execution-orchestrator 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 2d 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.

skills/execution-orchestrator/SKILL.md · 254 lines

How it starts

The opening of the file, as written. The whole thing — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Execution Orchestrator - Smart Hybrid Dispatch

Executes the task plan generated by the task-router by spawning agents with the right models, collecting results, and coordinating integration.

When to Activate

  • Called by task-router after generating an execution plan
  • When re-executing after a conflict resolution

Core Principle

Each agent is self-contained. When spawning an agent via the Agent tool:

  • Include ALL context the agent needs in its prompt
  • Include the Index-First Protocol
  • Include relevant skill guidance
  • Include the specific files/symbols to work on
  • Include expected output format
  • Include context carry-forward from previous task (if applicable, see below)
  • The agent should be able to complete its subtask with ZERO additional context

Context Carry-Forward

Before dispatching agents, check if context from the previous task can reduce re-reading:

  1. Read the last entry in .claude/crew-history.json
  2. Check if the previous task's filesModified overlaps with the current task's focus files
  3. If overlap exists AND the previous task was recent (same session):
    • Include a "Previous Context" section in the agent prompt (max 500 tokens):
      ## Previous Task Context
      The previous task ("{task description}") modified these overlapping files:
      - {file}: {summary of what changed}
      Key decisions: {summary field from history}
      
    • This helps agents understand recent changes without re-reading unchanged sections
  4. If no overlap or no recent history: skip this section

Token budget: Max 500 tokens for carry-forward context. If the previous summary is longer, condense to the most relevant parts for the current task's scope.

Execution Modes

Sequential Execution

For dependent subtasks where output of one feeds into the next:

Phase 1: Agent A completes → result
Phase 2: Agent B receives result + its task → completes → result
Phase 3: Agent C receives combined results → completes

Implementation:

  1. Spawn Agent A, wait for result
  2. Include Agent A's result summary in Agent B's prompt
  3. Spawn Agent B, wait for result
  4. Continue chain

Read the full file on GitHub · 254 lines

Changes

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.

  1. 2d ago First seen · 254 lines · 40 tokens per session scan A 1df6a07f91f7

Subscribe to this mod's changes

execution-orchestrator is a skill published in the GitHub repository d3x293/code-crew (13 stars, last pushed 4mo ago), licensed MIT. It adds 40 tokens to every session and 2,253 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-30.