explaingit

zypherhq/agent-orchestration-skill

Analysis updated 2026-06-24

30PythonAudience · developerComplexity · 3/5Setup · moderate

TLDR

A Codex Skill that gives a root agent a written contract plus Python helper scripts for batching work, sizing tasks, and stopping worker agents from spawning more workers.

Mindmap

mindmap
  root((agent-orchestration))
    Inputs
      Task description
      File and risk metrics
      Worker reports
    Outputs
      Dispatch packets
      Run ledger entries
      Dependency graph
    Use Cases
      Multi-agent coding runs
      Token budget control
      Worker fan-out limits
    Tech Stack
      Python
      Markdown contract
      OpenAI Codex Skills
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Cap fan-out in a Codex multi-agent run so worker sessions cannot spawn more workers

USE CASE 2

Classify a coding task into XS to XL sizes before dispatching workers

USE CASE 3

Generate per-worker dispatch packets that only include the files that worker owns

USE CASE 4

Run a plan gate on a DAG before any worker is allowed to start

What is it built with?

PythonMarkdownCodex

How does it compare?

zypherhq/agent-orchestration-skillkingbootoshi/goal-ledgerramkumarmn/hub_backend
Stars303030
LanguagePythonPythonPython
Setup difficultymoderateeasyhard
Complexity3/52/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · moderate Time to first run · 30min

Only useful if you already run Codex with the skills system, and must be loaded only by the root session.

In plain English

This repository packages a Skill for Codex, OpenAI's agent runtime, that aims to keep a multi-agent coding session organized and bounded. The author calls it a 'root-only' skill: it is meant to be loaded by the parent session that hands work to smaller worker sessions, and the worker sessions are forbidden from loading it or spawning further children of their own. The point is to prevent runaway fan-out where a parent asks a worker for help, the worker asks two more workers, and the token bill plus the confusion grow out of control. The skill ships as a single Markdown contract file with a set of rules the root session has to follow. Examples include batching work by user flow or area of the codebase instead of one worker per file, matching reasoning effort to the ambiguity and risk of the task, classifying a failure before retrying it, and sending each worker a short 'Dispatch Packet' with only what that worker needs instead of the full plan. The recommended workflow is short. The root session classifies the task by file count, surface area, risk, ambiguity, and verification needs, then picks one of five sizes from XS to XL. Non-trivial work gets a 'run ledger' folder that records the run, and medium or larger work gets a small dependency graph that has to pass a gate before any worker spawns. Around the Markdown rules the repo ships sixteen Python helper scripts. None of them call an AI model. They include a task classifier, a batcher, a budget checker, a DAG planner, a plan gate, a dispatch compiler, a run ledger writer, a handoff validator, a handoff router that flags overlapping file ownership, a failure classifier, a test command discoverer, a quality gate runner, a worktree creator for isolated runs, a small notepad for durable learnings, and a linter for installed skills. Installation is one 'npx skills add' command pointed at the GitHub URL, and the OpenAI manifest is set so that the skill only runs when explicitly requested, not automatically.

Copy-paste prompts

Prompt 1
Walk me through installing this skill with npx skills add and confirming the root-only manifest is set up
Prompt 2
Use the task classifier script to size a refactor that touches 8 files across two services
Prompt 3
Write a Dispatch Packet for a worker that only owns the auth module of my repo
Prompt 4
Plug the failure classifier into my CI loop so a flaky test gets retried but a real failure stops the run

Frequently asked questions

What is agent-orchestration-skill?

A Codex Skill that gives a root agent a written contract plus Python helper scripts for batching work, sizing tasks, and stopping worker agents from spawning more workers.

What language is agent-orchestration-skill written in?

Mainly Python. The stack also includes Python, Markdown, Codex.

How hard is agent-orchestration-skill to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is agent-orchestration-skill for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.