Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/vasilyu1983/AI-Agents-publicnpx agentmods add skills/vasilyu1983/ai-agents-public/agents-swarm-orchestrationWrote 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.
[](https://agentmods.dev/skills/vasilyu1983/ai-agents-public/agents-swarm-orchestration)<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/agents-swarm-orchestration"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/agents-swarm-orchestration/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.
<a href="https://agentmods.dev/skills/vasilyu1983/ai-agents-public/agents-swarm-orchestration"><img src="https://agentmods.dev/badge/skills/vasilyu1983/ai-agents-public/agents-swarm-orchestration.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00038 | $0.07456 |
| Opus 5 | $0.00019 | $0.03728 |
| Sonnet 5 | $0.00008 | $0.01491 |
| Haiku 4.5 | $0.00004 | $0.00746 |
Grade A, and why
agents-swarm-orchestration 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.
How it starts
The opening of the file, as written. The whole thing — 389 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swarm Orchestration
Advanced execution layer for multi-worker runs after agent or team selection.
Coordinate multiple workers without polluting the main thread. Use this skill after agents-subagents has already selected the right agent, member, team, or debate pattern. This skill is for choosing the orchestration surface, freezing task ownership before fan-out, and requiring structured outputs that the lead agent can validate and merge safely.
Terminology (Aug 2026)
"Swarm" is community vocabulary — it appears nowhere in Anthropic documentation. Use the official primitive names when writing configs, prompts, or docs; keep "swarm" only as informal shorthand for the whole category.
| Informal | Official primitive | Status (Aug 2026) |
|---|---|---|
| "swarm of subagents" | Subagents | GA. Background behavior is mode-dependent; background: true forces background but false is not a documented foreground pin. Recursive spawn currently defaults to three layers below the main session |
| "swarm with peer chat" | Agent teams | Experimental, env-gated CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1. Behavior churns weekly — re-verify before relying |
| "scripted swarm" | Dynamic workflows | Shipped 2026-05. JS in .claude/workflows/; ≤1000 agents/run, 16 concurrent. The repeatable-orchestration artifact |
| "swarm across terminals" | Cross-session messaging | Aug 2026, macOS/Linux. Sessions message each other without a team — lighter than teams for passing findings |
Quick Reference
| Situation | Default pattern | Why |
|---|---|---|
| 1-2 tasks or shared-file edits | Stay in the main conversation | Parallelism adds coordination overhead without payoff |
| Focused worker that only needs to report back | Claude Code subagent or Codex worker | Isolated context, simple coordination |
| Workers must talk to each other | Claude Code agent team | Shared task list plus direct messaging |
| Read-heavy scans, tests, triage, summarization | Parallel workers | Keeps noisy intermediate output off the lead thread |
| One coordinator should retain user ownership | Manager / agents-as-tools | Lead keeps control of decisions and final answer |
| Specialist should take over the conversation | Handoff | Ownership moves to the specialist agent |
| Work of unknown extent — discovery is the task | Loop until K empty rounds | A fixed task list cannot be enumerated up front |
| Loop Engineering: recurring discovery or evaluation | Loop-until-dry or budget-bounded loop | Define convergence, termination, and state checkpoints |
| Many items, known stages, high intermediate volume | Scripted workflow (Claude Code) | Script holds control flow; lead context holds only the result |
What ships with it
16 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 325 B
- data/sources.json 16 KB
- learnings.consolidated.md 602 B
- learnings.md 383 B
- references/cost-discipline.md 9.5 KB
- references/execution-surfaces.md 6.8 KB
- references/loop-orchestration.md 13 KB
- references/noninteractive-and-blueprints.md 5.6 KB
- references/operational-guardrails.md 8.4 KB
- references/orchestration-maintenance-runbook.md 7.4 KB
- references/output-contracts.md 3.5 KB
- references/platform-patterns.md 17 KB
- references/recipe-wave-dispatch.md 7.7 KB
- references/runtime-smoke-tests.md 8.4 KB
- references/scripted-workflows.md 13 KB
- references/typical-scenarios.md 12 KB
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.
- 9d ago Changed · +25 lines 9f0fad504fc8
- 13d ago First seen · 364 lines · 38 tokens per session scan A 49d7da800e16
agents-swarm-orchestration is a skill published in the GitHub repository vasilyu1983/AI-Agents-public (87 stars, last pushed 10d ago), licensed MIT. It adds 38 tokens to every session and 7,456 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-30.
Other skills, from other repositories
nft-standards
Implement NFT standards (ERC-721, ERC-1155) with proper metadata handling, minting strategies, and marketplace integration. Use when creating NFT contracts, building NFT marketplaces, or implementing digital asset systems.
istio-traffic-management
Configure Istio traffic management including routing, load balancing, circuit breakers, and canary deployments. Use when implementing service mesh traffic policies, progressive delivery, or resilience patterns.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
microservices-patterns
Design microservices architectures with service boundaries, event-driven communication, and resilience patterns. Use when building distributed systems, decomposing monoliths, or implementing microservices.
track-management
Use this skill when creating, managing, or working with Conductor tracks - the logical work units for features, bugs, and refactors. Applies to spec.md, plan.md, and track lifecycle operations.
make-pr-easy-to-review
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior. Use for "make this easy to review", "tidy this PR", "clean up commits", or "annotate the diff".