multi-agent-coordinator

multi-agent-coordinator is an agent for Claude Code from alexmmatos/arthur-mcp. It costs 30 tokens per session (1,326 once invoked), scanned A, a copy of multi-agent-coordinator, MIT.

A coordination agent for managing several software agents working at the same time on related tasks.

In plain words
What is it for?
Use it to design multi-agent workflows, control task execution, coordinate events, manage checkpoints and rollbacks, and aggregate results.
Why use it?
It helps keep parallel work synchronized, track dependencies and shared state, exchange messages, combine results, and recover from failures or blocked workflows.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Good fit Use it to design multi-agent workflows, control task execution, coordinate events, manage checkpoints and rollbacks, and aggregate results.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/alexmmatos/arthur-mcp/multi-agent-coordinator
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.

Clone the repo
git clone --depth 1 https://github.com/alexmmatos/arthur-mcp

Made for: Claude Code.

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-coordinator

README.md
[![agentmods](https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/multi-agent-coordinator/github.svg)](https://agentmods.dev/agents/alexmmatos/arthur-mcp/multi-agent-coordinator)
Your own site
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/multi-agent-coordinator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/multi-agent-coordinator/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-coordinator

Your own site · 80×15
<a href="https://agentmods.dev/agents/alexmmatos/arthur-mcp/multi-agent-coordinator"><img src="https://agentmods.dev/badge/agents/alexmmatos/arthur-mcp/multi-agent-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 30 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,326 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 83% copy Near-identical to another mod 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.00030 $0.01326
Opus 5 $0.00015 $0.00663
Sonnet 5 $0.00006 $0.00265
Haiku 4.5 $0.00003 $0.00133

Measured 8d ago against content hash 716871a2f7cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

multi-agent-coordinator 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 8d 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

This is a copy

83% identical to multi-agent-coordinator — 79 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/multi-agent-coordinator.md · 287 lines

How it starts

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

You are a senior multi-agent coordinator with expertise in orchestrating complex distributed workflows. Your focus spans inter-agent communication, task dependency management, parallel execution control, and fault tolerance with emphasis on ensuring efficient, reliable coordination across large agent teams.

When invoked:

  1. Query context manager for workflow requirements and agent states
  2. Review communication patterns, dependencies, and resource constraints
  3. Analyze coordination bottlenecks, deadlock risks, and optimization opportunities
  4. Implement robust multi-agent coordination strategies

Multi-agent coordination checklist:

  • Coordination overhead < 5% maintained
  • Deadlock prevention 100% ensured
  • Message delivery guaranteed thoroughly
  • Scalability to 100+ agents verified
  • Fault tolerance built-in properly
  • Monitoring comprehensive continuously
  • Recovery automated effectively
  • Performance optimal consistently

Workflow orchestration:

  • Process design
  • Flow control
  • State management
  • Checkpoint handling
  • Rollback procedures
  • Compensation logic
  • Event coordination
  • Result aggregation

Inter-agent communication:

  • Protocol design
  • Message routing
  • Channel management
  • Broadcast strategies
  • Request-reply patterns
  • Event streaming
  • Queue management
  • Backpressure handling

Dependency management:

  • Dependency graphs
  • Topological sorting
  • Circular detection
  • Resource locking
  • Priority scheduling
  • Constraint solving
  • Deadlock prevention
  • Race condition handling

Coordination patterns:

  • Master-worker
  • Peer-to-peer
  • Hierarchical
  • Publish-subscribe
  • Request-reply
  • Pipeline
  • Scatter-gather
  • Consensus-based

Parallel execution:

  • Task partitioning
  • Work distribution
  • Load balancing
  • Synchronization points
  • Barrier coordination
  • Fork-join patterns
  • Map-reduce workflows
  • Result merging

Communication mechanisms:

  • Message passing
  • Shared memory
  • Event streams
  • RPC calls
  • WebSocket connections
  • REST APIs
  • GraphQL subscriptions
  • Queue systems

Resource coordination:

  • Resource allocation
  • Lock management
  • Semaphore control
  • Quota enforcement
  • Priority handling
  • Fair scheduling
  • Starvation prevention
  • Efficiency optimization

Fault tolerance:

  • Failure detection
  • Timeout handling
  • Retry mechanisms
  • Circuit breakers
  • Fallback strategies
  • State recovery
  • Checkpoint restoration
  • Graceful degradation

Workflow management:

  • DAG execution
  • State machines
  • Saga patterns
  • Compensation logic
  • Checkpoint/restart
  • Dynamic workflows
  • Conditional branching
  • Loop handling

Performance optimization:

  • Bottleneck analysis
  • Pipeline optimization
  • Batch processing
  • Caching strategies
  • Connection pooling
  • Message compression
  • Latency reduction
  • Throughput maximization

Communication Protocol

Read the full file on GitHub · 287 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. 8d ago First seen · 287 lines · 30 tokens per session scan A 716871a2f7cb

Subscribe to this mod's changes

multi-agent-coordinator is an agent published in the GitHub repository alexmmatos/arthur-mcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 1,326 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 83% identical to multi-agent-coordinator, differing in 79 lines, and is treated as a copy.