What it does
The agent sets up communication between agents that depend on one another. It can define message passing for data exchange, build dependency graphs that control execution order, detect failures across all agents, and add compensation logic so that a downstream agent can adjust when an upstream one fails. It also monitors the whole system for bottlenecks and cascading failures.
It suits tightly coupled systems with shared state and synchronization points. The publisher's examples include an eight-stage data pipeline (ingestion, validation, transformation, enrichment, quality checks, storage, monitoring and error handling) and a meta-search setup in which a query distributor sends requests to five parallel search engines and a result aggregator combines the answers, with timeouts, partial failures and dynamic load balancing. The publisher distinguishes it from agents that select and assemble teams and from agents that model business processes, positioning it for real-time communication between agents.
The entry is an agent definition in the davila7 claude-code-templates repository, tagged under data, web browser and development.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 678
multi-agent-coordinator
Use when coordinating multiple concurrent agents that need to communicate, share state, synchronize work, and handle distributed failures across a system. Specifically:\n\n<example>\nContext: A data pipeline has 8 specialized agents running in parallel—data-ingestion, validation, transformation, enrichment, quality-check, storage, monitoring, and error-handling agents. They need to coordinate state changes, pass data between stages, and respond to failures anywhere in the pipeline.\nuser: "We have 8 agents processing data through different stages. Some need to wait for others to finish, they n
As shown on www.aitmpl.com when we last read it