multi-agent-orchestrator

multi-agent-orchestrator is a skill for Claude Code, Codex from ytunahankskn/oh-meine-excode. It costs 31 tokens per session (787 once invoked), scanned A, original, MIT.

A workflow for coordinating multiple coding agents, such as explorers, implementers, and reviewers, on one task.

In plain words
What is it for?
Use it to inspect an unfamiliar codebase, assign bounded implementation or verification tasks, run independent work in parallel, and integrate the results.
Why use it?
It keeps delegation focused and prevents agents from editing the same files or taking over the main agent's immediate blocking work.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents; mentions Codex.

Good fit Use it to inspect an unfamiliar codebase, assign bounded implementation or verification tasks, run independent work in parallel, and integrate the results.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator
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.

Any agent
npx skills add ytunahankskn/oh-meine-excode --skill multi-agent-orchestrator
Clone the repo
git clone --depth 1 https://github.com/ytunahankskn/oh-meine-excode

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for multi-agent-orchestrator

README.md
[![agentmods](https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator/github.svg)](https://agentmods.dev/skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator)
Your own site
<a href="https://agentmods.dev/skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator"><img src="https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for multi-agent-orchestrator

Your own site · 80×15
<a href="https://agentmods.dev/skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator"><img src="https://agentmods.dev/badge/skills/ytunahankskn/oh-meine-excode/multi-agent-orchestrator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 787 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00031 $0.00787
Opus 5 $0.00015 $0.00394
Sonnet 5 $0.00006 $0.00157
Haiku 4.5 $0.00003 $0.00079

Measured 9d ago against content hash 3426a888a43a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

multi-agent-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 9d 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.

plugins/oh-meine-excode/skills/multi-agent-orchestrator/SKILL.md · 112 lines

How it starts

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

Multi-Agent Orchestrator

Use this skill when the user explicitly wants delegation, multiple agents, parallel work, or a squad-style workflow.

This skill is designed for Codex's real capabilities:

  • explorer agents answer focused codebase questions
  • worker agents own bounded implementation or verification tasks
  • the main agent keeps urgent blocking work local and integrates results

Core Rules

  1. Make a short local plan before delegating.
  2. Keep the immediate blocking task local when the next step depends on it.
  3. Delegate only concrete, well-scoped side tasks that materially advance the work.
  4. Prefer disjoint ownership. Two workers should not edit the same file set unless absolutely necessary.
  5. Do not spawn subagents unless the user asked for parallel or delegated work.
  6. Do not wait on subagents reflexively. Continue with useful local work while they run.

Delegation Patterns

Pattern 1: Explore + Implement

Use when the codebase is unclear.

  • Keep the first local read of the critical path in the main thread.
  • Spawn one explorer to answer 1-2 specific codebase questions.
  • If there is a bounded implementation slice that can proceed independently, spawn one worker.
  • Integrate both results locally.

Pattern 2: Two-Worker Split

Use when the task can be partitioned cleanly.

  • Worker A owns one file or module group.
  • Worker B owns a disjoint file or module group.
  • The main agent handles integration, shared types, or final verification.

Pattern 3: Implement + Verify

Use when risk matters.

  • Main agent or worker performs the change.
  • Spawn an explorer or second worker for a targeted review or test gap check.
  • Integrate findings before finishing.

Spawn Guidance

explorer

Use for:

  • locating the right modules
  • finding framework conventions
  • tracing data flow
  • summarizing existing architecture
  • identifying likely review risks

The prompt should ask a concrete question and request a short answer with file references.

Read the full file on GitHub · 112 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. 9d ago First seen · 112 lines · 31 tokens per session scan A 3426a888a43a

Subscribe to this mod's changes

multi-agent-orchestrator is a skill published in the GitHub repository ytunahankskn/oh-meine-excode (2 stars, last pushed 5mo ago), licensed MIT. It adds 31 tokens to every session and 787 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-31.