multi-agent

A workflow for splitting one task among several AI agents, each assigned a role, provider, and model, then combining their results.

In plain words
What is it for?
Use it to define agent teams, send each phase to a suitable model, collect their work, and produce one result.
Why use it?
It organizes planning, implementation, and review across different AI systems instead of handling every phase in one pass.

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/adolfousier/opencrabs/multi-agent
Any agent
npx skills add adolfousier/opencrabs --skill multi-agent
Clone the repo
git clone --depth 1 https://github.com/adolfousier/opencrabs

Made for: Claude Code, Codex.

Per session 59 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,564 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00059 $0.01564
Opus 5 $0.00030 $0.00782
Sonnet 5 $0.00012 $0.00313
Haiku 4.5 $0.00006 $0.00156

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

Security

Grade A, and why

multi-agent scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s https://api.example.com/v1/chat/completions \
src/docs/reference/templates/skills/multi-agent/SKILL.md · 184 lines

How it starts

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

Multi-Agent Orchestration

You are orchestrating a task across a team of AI agents. Each team member has a role, a provider, and a model. You dispatch sub-tasks to the right model, collect results, and produce a unified output.

How It Works

When the user provides a task, follow this flow:

Phase 1 — Define the Team

If the user provides a team definition, use it. If not, propose a default team based on the task type. The team definition is a list of agents:

team:
  - role: planner
    provider: anthropic
    model: claude-opus-4-20250514
    task: "Analyze the request and produce a structured plan with clear steps, dependencies, and risks."
  - role: executor
    provider: openrouter
    model: google/gemini-2.5-pro
    task: "Execute each step of the plan. Write code, make changes, run commands."
  - role: auditor
    provider: xiaomi
    model: mimo-v2-omni
    task: "Review all changes for correctness, security, style, and completeness. Report issues."

Present the team to the user for confirmation before proceeding. The user can:

  • Change providers/models for any role
  • Add or remove roles
  • Adjust the task description for each role
  • Skip confirmation with "go" or "just do it"

Phase 2 — Execute Sequentially

Run each agent in order. For each agent:

  1. Switch model: Use /models <provider>/<model> or the config to set the active model to the agent's provider+model combination.

  2. Dispatch the task: Send the agent's task as a prompt, along with:

    • The original user request
    • Any output from previous agents (context handoff)
    • Specific instructions for this phase
  3. Collect output: Capture the full response. This becomes input for the next agent.

  4. Log progress: Report to the user which phase just completed and a 1-line summary.

Phase 3 — Synthesize

After all agents have run:

  1. Combine all outputs into a coherent result
  2. Highlight any conflicts or issues found by the auditor
  3. Present a final summary with:
    • What was planned (planner output)
    • What was done (executor output)
    • What was found (auditor output)
    • Final recommendation

Read the full file on GitHub · 184 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 · 184 lines · 59 tokens per session scan A 99422932e848

Subscribe to this mod's changes

multi-agent is a skill published in the GitHub repository adolfousier/opencrabs (916 stars, last pushed 3d ago), licensed MIT. It adds 59 tokens to every session and 1,564 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

compare-harnesses

Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.

ruvnet/metaharness · 66 tokens

oia-manifest

Emit .harness/oia-manifest.json declaring layer alignment with the OIA v0.1 9-layer reference architecture. Self-describes the harness's MCP wiring, witness signing, audit log, identity posture (always 'none' at v0.1). --check verifies an existing manifest, --dry-run prints without writing, --json emits to stdout.

ruvnet/metaharness · 79 tokens

create-harness

Scaffold your own focused AI agent harness — pick host (Claude Code, Codex, pi.dev, Hermes), template, agents, skills, and ship a npm-publishable harness with its own npx CLI. Use when a user asks to "create my own agent harness", "scaffold a harness", "make a custom Claude Code plugin like ruflo", or "build a…

ruvnet/metaharness · 89 tokens

diag-harness

Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.

ruvnet/metaharness · 85 tokens

example-harness

Scaffold a ready-made AI agent harness in one command from the 19 published @metaharness/ example packages — 9 host integrations (Claude Code, Codex, Hermes, pi.dev, OpenClaw, RVM, Copilot, OpenCode, GitHub Actions) + 10 vertical pods (devops, research, trading, support, legal, coding, education, sales, gaming…

ruvnet/metaharness · 90 tokens

repo-genome

7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.

ruvnet/metaharness · 73 tokens