Agent skill

Multi Model Orchestrator

by majiayu000 in majiayu000/spellbook

A skill your agent uses when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

MITAuto-check passedAgent Workflows

Install Multi Model Orchestrator

skills CLI
$ npx skills add majiayu000/spellbook --skill multi-model-orchestrator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install majiayu000/spellbook multi-model-orchestrator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/majiayu000/spellbook.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/multi-model-orchestrator .claude/skills/multi-model-orchestrator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
multi-model-orchestrator
GitHub stars
287
Token cost
~1.5k tokens
SKILL.md length
568 words
Files
11 (incl. references)
Skills in repo
97
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

  • Works in 4 steps: High-level planning — breaking down a… → Parallel execution — different agents… → Feedback synthesis — collecting results… → …
  • Coordinating complex tasks across multiple AI agents with a centralized handoff document for planning
  • SKILL.md covers Why This Skill, Operating Contract, When to Use and Core Concepts, plus 5 more sections
  • Calls codex

What it does

Multi Model Orchestrator is an agent skill from majiayu000/spellbook. Use when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. The skill folder holds 12 other files, including reference files (for example `README.md`, `references/add-auth-to-api.yaml` and `references/advanced-sync.md`).

It sits in Agent Workflows, covering Multi-agent orchestration. The repository describes itself as: Cross-runtime skills for Claude Code, Codex, and multi-agent workflows. The licence is MIT.

When your agent uses it

  • Coordinating complex tasks across multiple AI agents with a centralized handoff document for planning
  • Execution tracking
  • Feedback fusion

Example prompts

  • “/multi-model-orchestrator”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. High-level planning — breaking down a big goal into concrete subtasks
  2. Parallel execution — different agents handling different task types simultaneously
  3. Feedback synthesis — collecting results and iterating intelligently
  4. Full traceability — understanding who did what, why, and what changed

What it can do on your machine

Read from SKILL.md and the folder at commit ed52af7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • codex

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Multi Model Orchestrator loads about 1.5k tokens when it runs, and up to ~8k if it reads all its reference files. Until then it costs about 44 tokens; SKILL.md has 568 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from majiayu000/spellbook at commit ed52af7, republished under its MIT licence (© majiayu000). 568 words, ~1,507 tokens.

Download SKILL.mdSave it as .claude/skills/multi-model-orchestrator/SKILL.md (or your agent's skills folder). This skill also uses 10 other files; get the full folder from GitHub.
name
multi-model-orchestrator
description
Use when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

multi-model-orchestrator

Decompose. Execute. Synthesize.

A lightweight skill for coordinating work across multiple AI agents (Claude, Opus, Haiku, Codex, or any agent) using a single handoff document as the source of truth.

Why This Skill

Complex work often requires:

  1. High-level planning — breaking down a big goal into concrete subtasks
  2. Parallel execution — different agents handling different task types simultaneously
  3. Feedback synthesis — collecting results and iterating intelligently
  4. Full traceability — understanding who did what, why, and what changed

This skill provides the structure and templates to do this cleanly.

Operating Contract

Direct actions: create or update one handoff document as the source of truth, decompose the goal into executor-ready subtasks, assign explicit dependencies, record execution results, and synthesize feedback into next steps.

Escalate before: starting execution when the goal, constraints, executor choice, writable scope, or done criteria are ambiguous.

Evidence-backed pushback: reject unverified completion claims, vague agent outputs, missing acceptance criteria, or parallel assignments that touch shared writable files without explicit ordering.

Feedback loop: after each execution round, update the handoff with result, evidence, blockers, and next action before assigning follow-up work.

When to Use

✅ Use when:

  • A single-agent conversation would be too long or unfocused
  • You want to parallelize work across multiple specialized agents
  • You need to decompose a vague goal into specific, executor-ready tasks
  • You want to track decisions, changes, and feedback in one place
  • You're exploring multiple approaches simultaneously (A/B/C branches)

❌ Don't use when:

  • The task is simple and one agent can handle it end-to-end
  • You don't need to track who did what
  • Execution is strictly sequential with no parallelization
  • The task is exploratory with no clear structure

Core Concepts

Handoff Document (Handoff)

A YAML file that serves as the single source of truth. It contains:

  • Goal — what are we trying to accomplish?
  • Subtasks — who does what, and what does success look like?
  • Context — code references, prior decisions, constraints
  • Execution Tracking — who executed, what was the result, what blockers?
  • Feedback — iterations, changes, and learnings
Show full SKILL.md (241 more words)Show less
Agent Roles

You choose which agents execute which subtasks. Examples:

AgentBest For
Claude (or Fable)Planning, decomposition, architecture review, high-level strategy
OpusComplex reasoning, deep analysis, novel problem-solving
HaikuFast iteration, simple fixes, quick validation
CodexCode generation, refactoring, technical implementation
Claude CodeInteractive development, running code, verification
The Loop
1. Define Goal
    ↓
2. Fable/Claude decomposes into Handoff subtasks
    ↓
3. You assign subtasks to agents
    ↓
4. Agents execute in parallel or sequence
    ↓
5. You record results in Handoff
    ↓
6. Review, iterate, or complete

Quick Start

The full five-step walkthrough with copy-paste templates lives in references/quick-start.md. Summary:

  1. Create handoff — copy templates/handoff-template.yaml to .claude/handoffs/my-task.yaml.
  2. Decompose — ask Fable/Claude to break the goal into 3-5 subtasks; paste into subtasks.
  3. Execute — give each subtask's input to its assigned executor.
  4. Record — append the result to execution.rounds.
  5. Iterate or complete — update metadata.status toward complete.

Field-by-field reference: references/handoff-structure.md.

Complete Example

See references/add-auth-to-api.yaml for a real-world multi-agent execution walkthrough.

Using with Claude Code

  1. Save your handoff to .claude/handoffs/task.yaml
  2. Run: cat .claude/handoffs/task.yaml to load it in conversation
  3. Ask Claude to execute a subtask
  4. When done, update the handoff manually or using a script

For automation, see references/advanced-sync.md.

Using with Codex

Codex does not have handoff-specific subcommands. Use codex exec with a focused prompt that names the handoff file and the exact subtask:

bash
codex exec "Read .claude/handoffs/task.yaml. Execute subtask task-1 only. Return the result, blockers, files changed, and verification evidence."

For decomposition:

bash
codex exec "Read .claude/handoffs/task.yaml. Propose 3-5 YAML subtasks using goal.summary, goal.context, and goal.acceptance_criteria. Do not edit files."

Resources


Status: Production ready · License: MIT

© majiayu000, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 10 other files (references) in skills/multi-model-orchestrator of majiayu000/spellbook.

  • SKILL.md
  • LICENSE
  • README.md
  • references/add-auth-to-api.yaml
  • references/advanced-sync.md
  • references/best-practices.md
  • references/faq.md
  • references/handoff-structure.md
  • references/quick-start.md
  • references/workflow-patterns.md
  • templates/handoff-template.yaml

Open the folder on GitHubat commit ed52af7

Compare with similar skills

Multi Model Orchestrator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Multi Model Orchestrator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Multi Model Orchestrator this skillmajiayu000/spellbook287—~1.5kAutomated safety check: PassMIT
Orca CLIstablyai/orca89k2 repos~593Automated safety check: PassMIT
Paseo Advisor Second Opiniongetpaseo/paseo20k1 repos~756Automated safety check: PassCustom licence
O2 Review Loopopenobserve/openobserve22k—~3.7kAutomated safety check: PassAGPL-3.0
Paseo Committeegetpaseo/paseo20k1 repos~496Automated safety check: PassCustom licence
Mission Control Agent APIbuilderz-labs/mission-control6.3k—~2.1kAutomated safety check: PassMIT

Similar skills

  • Orca CLI

    stablyai/orca

    Operate Orca-managed worktrees, folder contexts, terminals, repos, automations, artifacts, skill sharing, worktree comments, and Orca's embedded browser…

    89k GitHub starsUsed in 2 repos~593 tokens
    Agent WorkflowsAuto-check passed
  • Launches one separate agent through Paseo to give a second opinion on the current task, with a self-contained briefing and no permission to edit files.

    20k GitHub starsUsed in 1 repo~756 tokens
    Agent WorkflowsAuto-check passed
  • O2 Review Loop

    openobserve/openobserve

    Splits a change into planner, coder and independent reviewer roles: you confirm a spec, a subagent implements it, and a separate reviewer checks each round's local WIP commit.

    22k GitHub stars~3.7k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Paseo Committee

    getpaseo/paseo

    Forms a two-agent committee with contrasting profiles to analyze a stuck problem in parallel, reconcile their views and return a consensus plan without editing files.

    20k GitHub starsUsed in 1 repo~496 tokens
    Agent WorkflowsAuto-check passed
  • Mission Control Agent API

    builderz-labs/mission-control

    Teaches an agent to use the Mission Control dashboard API: register, send heartbeats, fetch assigned tasks, report progress and disconnect, with API key auth.

    6.3k GitHub stars~2.1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed
  • Paseo Agent Handoff

    getpaseo/paseo

    Hands off the current task, including context, decisions and failed attempts, to a fresh agent through Paseo by writing a self-contained briefing prompt and launching that agent.

    20k GitHub starsUsed in 1 repo~606 tokens
    Agent WorkflowsAuto-check passed

More from majiayu000/spellbook

All 97 skills in this repo
  • Skill Ecosystem Doctor

    majiayu000/spellbook

    Audits and repairs how coding-agent Skills are owned, copied and exposed across runtimes, from canonical sources to quarantine and retirement.

    287 GitHub stars~3k tokensUpdated 2 days ago
    Auto-check passed
  • AGENTS.md Scaffold

    majiayu000/spellbook

    Scans a repository for real evidence and proposes, or on request writes, a small stack of root and scoped AGENTS.md files with validation commands and generated-file boundaries.

    287 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Product Demo Builder

    majiayu000/spellbook

    Plans, produces or diagnoses evidence-backed product demo videos: script, capture plan, pacing checks and verified final media built on real product behavior.

    287 GitHub stars~3.3k tokensUpdated 2 days ago
    Auto-check passed
  • Flowguard Task Guard

    majiayu000/spellbook

    Single entry point that routes long or ambiguous agent tasks, checks live state, bounds autonomous loops and leaves a resumable handoff.

    287 GitHub stars~2.1k tokensUpdated 2 days ago
    Auto-check passed
  • npm Supply Chain Check

    majiayu000/spellbook

    Scans a repository, its lockfiles and node_modules for known malicious npm package versions and install-time indicators, using a read-only Python scanner.

    287 GitHub stars~1.5k tokensUpdated 2 days ago
    Auto-check passed
  • Product Manager Toolkit

    majiayu000/spellbook

    Product management helpers: a RICE scoring script, an interview transcript analyzer and PRD templates for prioritizing features, synthesizing research and writing requirements.

    287 GitHub stars~2.2k tokensUpdated 2 days ago
    Auto-check passed

Categories

Questions about Multi Model Orchestrator

What does Multi Model Orchestrator do?

A skill your agent uses when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion. Multi Model Orchestrator is an agent skill from majiayu000/spellbook. Use when coordinating complex tasks across multiple AI agents with a centralized handoff document for planning, execution tracking, and feedback fusion.

When should I use Multi Model Orchestrator?

Multi Model Orchestrator fits situations like: coordinating complex tasks across multiple AI agents with a centralized handoff document for planning; execution tracking; feedback fusion.

How do I install Multi Model Orchestrator in Claude Code?

Run `npx skills add majiayu000/spellbook --skill multi-model-orchestrator -a claude-code`. Or copy the skill folder (skills/multi-model-orchestrator in majiayu000/spellbook) into .claude/skills/multi-model-orchestrator in your project. Claude Code loads it when a task matches its description.

How do I install Multi Model Orchestrator in Codex?

Run `npx skills add majiayu000/spellbook --skill multi-model-orchestrator -a codex`. Or copy the skill folder (skills/multi-model-orchestrator in majiayu000/spellbook) into .agents/skills/multi-model-orchestrator in your project. Codex loads it when a task matches its description.

Can I use Multi Model Orchestrator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add majiayu000/spellbook --skill multi-model-orchestrator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/multi-model-orchestrator, .gemini/skills/multi-model-orchestrator, .github/skills/multi-model-orchestrator and .opencode/skills/multi-model-orchestrator in your project.

What does Multi Model Orchestrator need to run?

Going by SKILL.md and its folder, Multi Model Orchestrator needs the command-line tools its instructions call (codex).

Does Multi Model Orchestrator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Multi Model Orchestrator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Multi Model Orchestrator use?

Multi Model Orchestrator is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Multi Model Orchestrator use?

About 1.5k tokens (SKILL.md is roughly 6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 6.5k tokens, read only when the agent opens those files.

What are the alternatives to Multi Model Orchestrator?

Skills that share tags, products or a category with Multi Model Orchestrator: Orca CLI (stablyai/orca, 89k stars), Paseo Advisor Second Opinion (getpaseo/paseo, 20k stars), O2 Review Loop (openobserve/openobserve, 22k stars) and Paseo Committee (getpaseo/paseo, 20k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Multi Model Orchestrator?

majiayu000 (a GitHub user) maintains it in majiayu000/spellbook, which has 287 GitHub stars. The repository holds 97 skills in this directory. The repository was last updated on October 8, 2026.

Source: majiayu000/spellbook on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.