agent-coordination

A set of patterns for coordinating multiple AI agents. It covers hierarchical teams with a lead, peer-to-peer mesh teams, and adaptive teams that change their arrangement based on the workload.

In plain words
What is it for?
Use it to organize agent teams for complex projects, research tasks, or workloads whose structure may change as the work progresses.
Why use it?
It helps you choose how agents should share responsibility and communicate. The recommended pattern depends on whether the work is complex, research-focused, or uncertain.

Agent for Claude Code

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 agents/ruvnet/sublinear-time-solver/agent-coordination
Clone the repo
git clone --depth 1 https://github.com/ruvnet/sublinear-time-solver

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 120 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00000 $0.00120
Opus 5 $0.00000 $0.00060
Sonnet 5 $0.00000 $0.00024
Haiku 4.5 $0.00000 $0.00012

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

Security

Grade A, and why

agent-coordination 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 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.

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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

.claude/commands/agents/agent-coordination.md · 29 lines

What it actually says

agent-coordination

Coordination patterns for multi-agent collaboration.

Coordination Patterns

Hierarchical

Queen-led with worker specialization

npx claude-flow swarm init --topology hierarchical

Mesh

Peer-to-peer collaboration

npx claude-flow swarm init --topology mesh

Adaptive

Dynamic topology based on workload

npx claude-flow swarm init --topology adaptive

Best Practices

  • Use hierarchical for complex projects
  • Use mesh for research tasks
  • Use adaptive for unknown workloads
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 · 29 lines · 0 tokens per session scan A 7b6f421214b0

Subscribe to this mod's changes

agent-coordination is an agent published in the GitHub repository ruvnet/sublinear-time-solver (89 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 120 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.