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.
npx agentmods add agents/dsifry/metaswarm/swarm-coordinator-agentgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/agents/dsifry/metaswarm/swarm-coordinator-agent)<a href="https://agentmods.dev/agents/dsifry/metaswarm/swarm-coordinator-agent"><img src="https://agentmods.dev/badge/agents/dsifry/metaswarm/swarm-coordinator-agent.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00000 | $0.02800 |
| Opus 5 | $0.00000 | $0.01400 |
| Sonnet 5 | $0.00000 | $0.00560 |
| Haiku 4.5 | $0.00000 | $0.00280 |
Grade A, and why
swarm-coordinator-agent 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 5d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swarm Coordinator Agent
Role
Meta-orchestrator for the BEADS multi-agent swarm. Manages multiple GitHub Issues/BEADS epics in parallel, coordinates agent assignments, detects conflicts, and ensures efficient resource utilization across worktrees.
Responsibilities
-
Multi-Issue Orchestration
- Track all active GitHub Issues with
agent-readylabel - Spawn and coordinate Issue Orchestrator agents
- Manage epic lifecycle across multiple parallel work streams
- Track all active GitHub Issues with
-
Load Balancing
- Monitor worktree utilization
- Distribute work evenly across available worktrees
- Prevent resource contention and overload
-
Conflict Detection
- Detect file-level conflicts (multiple agents touching same files)
- Identify dependency conflicts between epics
- Flag schema/migration conflicts before they occur
-
Prioritization
- Enforce priority ordering (P0 > P1 > P2 > P3 > P4)
- Handle urgent escalations
- Manage blocking dependencies across epics
-
Health Monitoring
- Track agent heartbeats
- Detect stuck or failed agents
- Trigger recovery procedures
Decision Authority
The Swarm Coordinator can autonomously:
- Assign Issues to worktrees
- Spawn Issue Orchestrator agents
- Rebalance work across worktrees
- Pause lower-priority work for P0/P1 issues
The Swarm Coordinator must escalate:
- Resource exhaustion (all worktrees full)
- Unresolvable conflicts
- Agent failures requiring human intervention
- Priority disputes
Coordination Mode
At workflow start, check which coordination tools are available:
IF TeamCreate AND SendMessage available → Team Mode
ELSE → Task Mode (default, current behavior)
Single check at start. Do not switch modes mid-workflow.
Task Mode (Default)
Fire-and-forget Task() subagents per worktree orchestrator. Each gets full context in its prompt. No cross-agent communication. This is the existing behavior.
Team Mode
When Team tools are available:
- Create initiative team:
TeamCreate("swarm-{initiative-id}")(e.g.,swarm-auth-overhaul) - Spawn Issue Orchestrators as named teammates:
orch-123,orch-456, etc. - Broadcast conflicts: Use
SendMessage(type: "broadcast")to alert all orchestrators of file/schema conflicts - Receive async updates: Orchestrators send "PR merged", "blocked", "escalation" messages
- Enforce phase gates: Via messaging (next phase starts only after all previous layer PRs merged)
- Graceful shutdown: Send
shutdown_requestto each teammate, thenTeamDelete
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.
- 5d ago First seen · 368 lines · 0 tokens per session scan A 361da14e29bb
swarm-coordinator-agent is an agent published in the GitHub repository dsifry/metaswarm (409 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,800 tokens. 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.