What is multi-agent-coordinator?

A coordinator for workflows involving multiple software agents. It manages communication, task dependencies, parallel work, shared state, failures, and combining results.

Use it to design multi-agent workflows, sequence dependent tasks, coordinate parallel execution, handle checkpoints and rollbacks, and aggregate results.

It helps prevent agents from blocking one another, duplicating work, losing progress, or producing results without the needed dependencies.

How 2SSK/dot-files configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to 2SSK/dot-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/2SSK/dot-files/main/.claude/agents/multi-agent-coordinator.md

Clone the repo

git clone --depth 1 https://github.com/2SSK/dot-files

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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/2ssk/dot-files/multi-agent-coordinator/github.svg)](https://agentmods.dev/agents/2ssk/dot-files/multi-agent-coordinator)

Your own site

<a href="https://agentmods.dev/agents/2ssk/dot-files/multi-agent-coordinator"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/2ssk/dot-files/multi-agent-coordinator"><img src="https://agentmods.dev/badge/agents/2ssk/dot-files/multi-agent-coordinator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 81 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,390 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 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.

Model	Per session	Once invoked
Fable 5.1	$0.00081	$0.01390
Opus 5.5	$0.00032	$0.00556
Sonnet 5.5	$0.00016	$0.00278
Haiku 4.5	$0.00008	$0.00139

Measured 14d ago against content hash 40d841208af1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 14d 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

4 near-identical copies found in the catalogue:

multi-agent-coordinator — 91% identical, 97 lines differ
multi-agent-coordinator — 91% identical, 97 lines differ
multi-agent-coordinator — 88% identical, 97 lines differ
multi-agent-coordinator — 80% identical, 166 lines differ

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

How it starts

The opening of the file, as written. The whole thing — 316 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

Read the full file on GitHub · 316 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.

14d ago First seen · 316 lines · 81 tokens per session scan A 40d841208af1

Subscribe to this mod's changes

multi-agent-coordinator is an agent published in the GitHub repository 2SSK/dot-files (250 stars, last pushed yesterday), licensed MIT. It adds 81 tokens to every session and 1,390 once invoked, about $0.0003 per session on Opus 5.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-10-02.

Building agents Featured i3 linux rice sway

osc-triage

Block 1 of the openSUSE-packaging pipeline. Use to find out whether a package (or all of a maintainer's packages) is out of date, before any update work. Enumerates maintained packages, compares against upstream, and returns a verified candidate list with false positives filtered out.

openSUSE/openSUSE-packaging-skill · 65 tokens

dot-files: Agent for Claude Code