Share complete, opinionated combinations of a Codex lead agent and specialist subagents. Choose an arrangement, install its TOMLs and instructions, and adapt it to your work. You do not need any private framework, MCP server or paid third-party orchestration service to use these files.
Guia em português · Installation · Contributing · Orchestration rationale · Skills · Plugins · Validation and compatibility
Version 0.5.0 is a community preview. Historical hook and selected-role tests are recorded; the revised allocations and caps are not fully runtime-certified.
| Arrangement | Lead | Specialist allocation | Configured cap / recommended active children |
|---|---|---|---|
| Advanced Delivery | gpt-6-sol, xhigh |
15 roles: 4 Astra, 4 Sol, 7 Luna | 4 / up to 3 |
| Balanced Delivery | gpt-6-sol, xhigh |
12 roles: 2 Astra, 2 Sol, 8 Luna | 4 / up to 3 |
| Lean Delivery | gpt-6-sol, high |
8 roles: 1 Astra, 1 Sol, 6 Luna | 3 / up to 2 |
The three arrangements provide progressively smaller role catalogs and enable Multi-Agent V2. Roles are available choices, not agents started together. Allocate only useful, independent work; parallel calls consume additional model tokens.
All three use a one-minute minimum and five-minute default for native child waits. Adaptive waiting explains how to choose task-appropriate windows and reduce empty polling without changing budgets. This is not a measured quota-savings guarantee.
Advanced Delivery targets complex product work and spends more of its model
allocation on design, advice, critical review and coupled implementation.
Balanced Delivery reserves Astra for advice and coupled implementation, and Sol
for backend implementation and integration review. Lean Delivery uses Luna
broadly, keeps Astra for read-only advice, and uses Sol high to review integration
across deliveries. Lean backend and frontend implementation use Luna. If ambiguity or business risk exceeds the selected
role's capability, the lead reassesses the assignment before continuing.
These are routing objectives, not measured cost or quality guarantees; total
cost also depends on task length, retries and parallelism.
The explicit V2 cap includes the lead in the target runtime. The child recommendations above reserve that slot. Recheck compatibility evidence when upgrading the runtime or changing the cap's configuration field.
- A small
config.tomlfragment and standaloneagents/*.tomlfiles. - A self-contained AGENTS.md snippet, or a variant with inline triggers for the optional codex-orchestration and pragmatic-programmer skills.
- An optional spawn-contract hook that checks explicit role selection and fresh-context delegation where the runtime intercepts spawn calls.
- A manifest describing the package, its author, license and runtime baseline.
Installation is manual. Merge only the documented settings into your existing configuration; your credentials, permissions, tools and MCP configuration remain your responsibility. Choosing an arrangement does not grant its agents new permissions.
Start with an existing arrangement, choose a distinct directory name, explain the tradeoffs and include functional evidence. Skills, plugins and hooks are optional. The contribution guide defines the package contract and checks. Submit a pull request; do not upload your entire Codex home.
You can contribute a new combination or improve an existing one. Public source, configuration, instructions, issues and PRs use English; translated documentation guides are welcome. See the changelog for published changes.
Components live outside the arrangements so they can serve any arrangement, another community combination, or an existing workflow:
- skills/: standalone, optional skills, including
codex-orchestrationandpragmatic-programmer. - plugins/: independently contributed plugin packages that may bundle skills, public MCP configurations and hooks.
- hooks/: independently installable hook components.
The first release includes two skills and one standalone hook, not an installable plugin bundle. Plugin contributions follow the official package format and need their own installation and runtime evidence. No component is enabled by choosing an arrangement.
The catalog, agent configurations and hook are MIT licensed. The adapted skills carry their own Apache-2.0 licenses and notices. Preserve the applicable license files when redistributing components.