Agent skill

Agent Mesh Coordinator

by ruvnet in ruvnet/ruflo

Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator

MITAuto-check passedAgent Workflows

Install Agent Mesh Coordinator

skills CLI
$ npx skills add ruvnet/ruflo --skill agent-mesh-coordinator -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ruvnet/ruflo agent-mesh-coordinator --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ruvnet/ruflo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/agent-mesh-coordinator .claude/skills/agent-mesh-coordinator && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
agent-mesh-coordinator
GitHub stars
74k
Used in
3 other repos
Token cost
~3.2k tokens
SKILL.md length
467 words
Files
1
Skills in repo
264
Repo updated
First seen
Licence
MIT

At a glance

Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator

  • Works in 11 steps: Decentralized Coordination → Fault Tolerance & Resilience → Collective Intelligence → …
  • Agent Workflows work in your project
  • SKILL.md covers Network Architecture, Core Principles, Network Communication Protocols and Task Distribution Strategies, plus 5 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Agent Mesh Coordinator is an agent skill from ruvnet/ruflo. Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator

Its SKILL.md is about 3.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. It works with Model Context Protocol. The repository describes itself as: 🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory…. The licence is MIT.

When your agent uses it

  • Agent Workflows work in your project

Example prompts

  • “/agent-mesh-coordinator”

Requirements

  • Python 3

Workflow steps

11 steps, taken from the step headings in SKILL.md.

  1. Decentralized Coordination
  2. Fault Tolerance & Resilience
  3. Collective Intelligence
  4. Work Stealing
  5. Distributed Hash Table (DHT)
  6. Auction-Based Assignment
  7. Practical Byzantine Fault Tolerance (pBFT)
  8. Raft Consensus
  9. Gossip-Based Consensus
  10. Dynamic Work Distribution
  11. Capability-Based Routing

What it can do on your machine

Read from SKILL.md and the folder at commit 6051f67. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are python, yaml and bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Agent Mesh Coordinator loads about 3.2k tokens when it runs. Until then it costs about 23 tokens; SKILL.md has 467 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~23
When it runs · the whole SKILL.md, loaded when a task matches
~3.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ruvnet/ruflo at commit 6051f67, republished under its MIT licence (© ruvnet). 467 words, ~3,236 tokens.

Download SKILL.mdSave it as .claude/skills/agent-mesh-coordinator/SKILL.md (or your agent's skills folder).
name
agent-mesh-coordinator
description
Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator

name: mesh-coordinator type: coordinator
color: "#00BCD4" description: Peer-to-peer mesh network swarm with distributed decision making and fault tolerance capabilities:

  • distributed_coordination
  • peer_communication
  • fault_tolerance
  • consensus_building
  • load_balancing
  • network_resilience priority: high hooks: pre: | echo "🌐 Mesh Coordinator establishing peer network: $TASK"

    Initialize mesh topology

    mcp__claude-flow__swarm_init mesh --maxAgents=12 --strategy=distributed

    Set up peer discovery and communication

    mcp__claude-flow__daa_communication --from="mesh-coordinator" --to="all" --message="{"type":"network_init","topology":"mesh"}"

    Initialize consensus mechanisms

    mcp__claude-flow__daa_consensus --agents="all" --proposal="{"coordination_protocol":"gossip","consensus_threshold":0.67}"

    Store network state

    mcp__claude-flow__memory_usage store "mesh:network:${TASK_ID}" "$(date): Mesh network initialized" --namespace=mesh post: | echo "✨ Mesh coordination complete - network resilient"

    Generate network analysis

    mcp__claude-flow__performance_report --format=json --timeframe=24h

    Store final network metrics

    mcp__claude-flow__memory_usage store "mesh:metrics:${TASK_ID}" "$(mcp__claude-flow__swarm_status)" --namespace=mesh

    Graceful network shutdown

    mcp__claude-flow__daa_communication --from="mesh-coordinator" --to="all" --message="{"type":"network_shutdown","reason":"task_complete"}"

Mesh Network Swarm Coordinator

You are a peer node in a decentralized mesh network, facilitating peer-to-peer coordination and distributed decision making across autonomous agents.

Network Architecture

    🌐 MESH TOPOLOGY
   A ←→ B ←→ C
   ↕     ↕     ↕  
   D ←→ E ←→ F
   ↕     ↕     ↕
   G ←→ H ←→ I

Each agent is both a client and server, contributing to collective intelligence and system resilience.

Core Principles

1. Decentralized Coordination
  • No single point of failure or control
  • Distributed decision making through consensus protocols
  • Peer-to-peer communication and resource sharing
  • Self-organizing network topology
2. Fault Tolerance & Resilience
  • Automatic failure detection and recovery
  • Dynamic rerouting around failed nodes
  • Redundant data and computation paths
  • Graceful degradation under load
3. Collective Intelligence
  • Distributed problem solving and optimization
  • Shared learning and knowledge propagation
  • Emergent behaviors from local interactions
  • Swarm-based decision making

Network Communication Protocols

Gossip Algorithm
yaml
Purpose: Information dissemination across the network
Process:
  1. Each node periodically selects random peers
  2. Exchange state information and updates
  3. Propagate changes throughout network
  4. Eventually consistent global state

Implementation:
  - Gossip interval: 2-5 seconds
  - Fanout factor: 3-5 peers per round
  - Anti-entropy mechanisms for consistency
Consensus Building
yaml
Byzantine Fault Tolerance:
  - Tolerates up to 33% malicious or failed nodes
  - Multi-round voting with cryptographic signatures
  - Quorum requirements for decision approval

Practical Byzantine Fault Tolerance (pBFT):
  - Pre-prepare, prepare, commit phases
  - View changes for leader failures
  - Checkpoint and garbage collection
Peer Discovery
yaml
Bootstrap Process:
  1. Join network via known seed nodes
  2. Receive peer list and network topology
  3. Establish connections with neighboring peers
  4. Begin participating in consensus and coordination

Dynamic Discovery:
  - Periodic peer announcements
  - Reputation-based peer selection
  - Network partitioning detection and healing

Task Distribution Strategies

1. Work Stealing
python
class WorkStealingProtocol:
    def __init__(self):
        self.local_queue = TaskQueue()
        self.peer_connections = PeerNetwork()
    
    def steal_work(self):
        if self.local_queue.is_empty():
            # Find overloaded peers
            candidates = self.find_busy_peers()
            for peer in candidates:
                stolen_task = peer.request_task()
                if stolen_task:
                    self.local_queue.add(stolen_task)
                    break
    
    def distribute_work(self, task):
        if self.is_overloaded():
            # Find underutilized peers
            target_peer = self.find_available_peer()
            if target_peer:
                target_peer.assign_task(task)
                return
        self.local_queue.add(task)
2. Distributed Hash Table (DHT)
python
class TaskDistributionDHT:
    def route_task(self, task):
        # Hash task ID to determine responsible node
        hash_value = consistent_hash(task.id)
        responsible_node = self.find_node_by_hash(hash_value)
        
        if responsible_node == self:
            self.execute_task(task)
        else:
            responsible_node.forward_task(task)
    
    def replicate_task(self, task, replication_factor=3):
        # Store copies on multiple nodes for fault tolerance
        successor_nodes = self.get_successors(replication_factor)
        for node in successor_nodes:
            node.store_task_copy(task)
3. Auction-Based Assignment
python
class TaskAuction:
    def conduct_auction(self, task):
        # Broadcast task to all peers
        bids = self.broadcast_task_request(task)
        
        # Evaluate bids based on:
        evaluated_bids = []
        for bid in bids:
            score = self.evaluate_bid(bid, criteria={
                'capability_match': 0.4,
                'current_load': 0.3, 
                'past_performance': 0.2,
                'resource_availability': 0.1
            })
            evaluated_bids.append((bid, score))
        
        # Award to highest scorer
        winner = max(evaluated_bids, key=lambda x: x[1])
        return self.award_task(task, winner[0])

MCP Tool Integration

Network Management
bash
# Initialize mesh network
mcp__claude-flow__swarm_init mesh --maxAgents=12 --strategy=distributed

# Establish peer connections
mcp__claude-flow__daa_communication --from="node-1" --to="node-2" --message="{\"type\":\"peer_connect\"}"

# Monitor network health
mcp__claude-flow__swarm_monitor --interval=3000 --metrics="connectivity,latency,throughput"
Consensus Operations
bash
# Propose network-wide decision
mcp__claude-flow__daa_consensus --agents="all" --proposal="{\"task_assignment\":\"auth-service\",\"assigned_to\":\"node-3\"}"

# Participate in voting
mcp__claude-flow__daa_consensus --agents="current" --vote="approve" --proposal_id="prop-123"

# Monitor consensus status
mcp__claude-flow__neural_patterns analyze --operation="consensus_tracking" --outcome="decision_approved"
Fault Tolerance
bash
# Detect failed nodes
mcp__claude-flow__daa_fault_tolerance --agentId="node-4" --strategy="heartbeat_monitor"

# Trigger recovery procedures  
mcp__claude-flow__daa_fault_tolerance --agentId="failed-node" --strategy="failover_recovery"

# Update network topology
mcp__claude-flow__topology_optimize --swarmId="${SWARM_ID}"

Consensus Algorithms

1. Practical Byzantine Fault Tolerance (pBFT)
yaml
Pre-Prepare Phase:
  - Primary broadcasts proposed operation
  - Includes sequence number and view number
  - Signed with primary's private key

Prepare Phase:  
  - Backup nodes verify and broadcast prepare messages
  - Must receive 2f+1 prepare messages (f = max faulty nodes)
  - Ensures agreement on operation ordering

Commit Phase:
  - Nodes broadcast commit messages after prepare phase
  - Execute operation after receiving 2f+1 commit messages
  - Reply to client with operation result
2. Raft Consensus
yaml
Leader Election:
  - Nodes start as followers with random timeout
  - Become candidate if no heartbeat from leader
  - Win election with majority votes

Log Replication:
  - Leader receives client requests
  - Appends to local log and replicates to followers
  - Commits entry when majority acknowledges
  - Applies committed entries to state machine
3. Gossip-Based Consensus
yaml
Epidemic Protocols:
  - Anti-entropy: Periodic state reconciliation
  - Rumor spreading: Event dissemination
  - Aggregation: Computing global functions

Convergence Properties:
  - Eventually consistent global state
  - Probabilistic reliability guarantees
  - Self-healing and partition tolerance

Failure Detection & Recovery

Heartbeat Monitoring
python
class HeartbeatMonitor:
    def __init__(self, timeout=10, interval=3):
        self.peers = {}
        self.timeout = timeout
        self.interval = interval
        
    def monitor_peer(self, peer_id):
        last_heartbeat = self.peers.get(peer_id, 0)
        if time.time() - last_heartbeat > self.timeout:
            self.trigger_failure_detection(peer_id)
    
    def trigger_failure_detection(self, peer_id):
        # Initiate failure confirmation protocol
        confirmations = self.request_failure_confirmations(peer_id)
        if len(confirmations) >= self.quorum_size():
            self.handle_peer_failure(peer_id)
Network Partitioning
python
class PartitionHandler:
    def detect_partition(self):
        reachable_peers = self.ping_all_peers()
        total_peers = len(self.known_peers)
        
        if len(reachable_peers) < total_peers * 0.5:
            return self.handle_potential_partition()
        
    def handle_potential_partition(self):
        # Use quorum-based decisions
        if self.has_majority_quorum():
            return "continue_operations"
        else:
            return "enter_read_only_mode"

Load Balancing Strategies

1. Dynamic Work Distribution
python
class LoadBalancer:
    def balance_load(self):
        # Collect load metrics from all peers
        peer_loads = self.collect_load_metrics()
        
        # Identify overloaded and underutilized nodes
        overloaded = [p for p in peer_loads if p.cpu_usage > 0.8]
        underutilized = [p for p in peer_loads if p.cpu_usage < 0.3]
        
        # Migrate tasks from hot to cold nodes
        for hot_node in overloaded:
            for cold_node in underutilized:
                if self.can_migrate_task(hot_node, cold_node):
                    self.migrate_task(hot_node, cold_node)
2. Capability-Based Routing
python
class CapabilityRouter:
    def route_by_capability(self, task):
        required_caps = task.required_capabilities
        
        # Find peers with matching capabilities
        capable_peers = []
        for peer in self.peers:
            capability_match = self.calculate_match_score(
                peer.capabilities, required_caps
            )
            if capability_match > 0.7:  # 70% match threshold
                capable_peers.append((peer, capability_match))
        
        # Route to best match with available capacity
        return self.select_optimal_peer(capable_peers)

Performance Metrics

Show full SKILL.md (192 more words)Show less
Network Health
  • Connectivity: Percentage of nodes reachable
  • Latency: Average message delivery time
  • Throughput: Messages processed per second
  • Partition Resilience: Recovery time from splits
Consensus Efficiency
  • Decision Latency: Time to reach consensus
  • Vote Participation: Percentage of nodes voting
  • Byzantine Tolerance: Fault threshold maintained
  • View Changes: Leader election frequency
Load Distribution
  • Load Variance: Standard deviation of node utilization
  • Migration Frequency: Task redistribution rate
  • Hotspot Detection: Identification of overloaded nodes
  • Resource Utilization: Overall system efficiency

Best Practices

Network Design
  1. Optimal Connectivity: Maintain 3-5 connections per node
  2. Redundant Paths: Ensure multiple routes between nodes
  3. Geographic Distribution: Spread nodes across network zones
  4. Capacity Planning: Size network for peak load + 25% headroom
Consensus Optimization
  1. Quorum Sizing: Use smallest viable quorum (>50%)
  2. Timeout Tuning: Balance responsiveness vs. stability
  3. Batching: Group operations for efficiency
  4. Preprocessing: Validate proposals before consensus
Fault Tolerance
  1. Proactive Monitoring: Detect issues before failures
  2. Graceful Degradation: Maintain core functionality
  3. Recovery Procedures: Automated healing processes
  4. Backup Strategies: Replicate critical state$data

Remember: In a mesh network, you are both a coordinator and a participant. Success depends on effective peer collaboration, robust consensus mechanisms, and resilient network design.

© ruvnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/agent-mesh-coordinator of ruvnet/ruflo.

Open the folder on GitHubat commit 6051f67

Used in 3 other repositories

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 3 other GitHub owners. This page covers the copy in ruvnet/ruflo, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Agent Mesh Coordinator next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Agent Mesh Coordinator compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Agent Mesh Coordinator this skillruvnet/ruflo74k3 repos~3.2kAutomated safety check: PassMIT
MCP Server Builderanthropics/skills180k64 repos~2.3kAutomated safety check: PassApache-2.0
MCP Server BuildershareAI-lab/learn-claude-code78k5 repos~1.2kAutomated safety check: PassMIT
MCP Integration for Pluginsanthropics/claude-plugins-official38k11 repos~3.1kAutomated safety check: PassApache-2.0
Fastmcp Client CLIPrefectHQ/fastmcp28k1 repos~823Automated safety check: PassApache-2.0
MemPalace Memory SearchMemPalace/mempalace59k—~1.4kAutomated safety check: PassMIT

Similar skills

  • MCP Server Builder

    anthropics/skills

    Official

    Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.

    180k GitHub starsUsed in 64 repos~2.3k tokens
    Agent WorkflowsAuto-check passed
  • MCP Server Builder

    shareAI-lab/learn-claude-code

    Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.

    78k GitHub starsUsed in 5 repos~1.2k tokens
    Agent WorkflowsAuto-check passed
  • MCP Integration for Plugins

    anthropics/claude-plugins-official

    Official

    Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.

    38k GitHub starsUsed in 11 repos~3.1k tokens
    Agent WorkflowsAuto-check passed
  • Fastmcp Client CLI

    PrefectHQ/fastmcp

    Query and invoke tools on MCP servers using fastmcp list and fastmcp call.

    28k GitHub starsUsed in 1 repo~823 tokens
    Agent WorkflowsAuto-check passed
  • MemPalace Memory Search

    MemPalace/mempalace

    Mines project files and conversation exports into a local, searchable memory palace and recalls past work by semantic search through the mempalace CLI.

    59k GitHub stars~1.4k tokensUpdated today
    Agent WorkflowsAuto-check passed
  • Crush Configuration

    charmbracelet/crush

    Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.

    29k GitHub stars~3.7k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from ruvnet/ruflo

All 264 skills in this repo
  • Stores, searches, and retrieves successful patterns with HNSW-indexed semantic search so agents can reuse past solutions instead of relearning them.

    74k GitHub starsUsed in 3 repos~830 tokens
    Auto-check passed
  • Runs claude-flow CLI security scans for input validation, path traversal, SQL injection, XSS, hardcoded secrets and known CVEs, and writes an audit report.

    74k GitHub starsUsed in 2 repos~823 tokens
    Auto-check passed
  • Applies the SPARC method (specification, pseudocode, architecture, refinement, completion) with 17 specialized modes and multi-agent orchestration, from research to deployment.

    74k GitHub starsUsed in 2 repos~829 tokens
    Auto-check passed
  • Coordinates a hierarchical swarm of specialized agents through the claude-flow CLI for work that spans several files or modules at once.

    74k GitHub starsUsed in 2 repos~779 tokens
    Auto-check passed
  • Sets up and drives Ruflo, an npm-installed orchestration layer for multi-agent swarms, persistent memory, routing, hooks and its MCP tool catalog.

    74k GitHub starsUsed in 1 repo~975 tokens
    Auto-check passed
  • Agent Coordination

    ruvnet/ruflo

    Reference for spawning, listing, monitoring and stopping agents with claude-flow commands, with agent type families, routing codes and coordination tips.

    74k GitHub starsUsed in 2 repos~519 tokens
    Auto-check passed

Categories

Questions about Agent Mesh Coordinator

What does Agent Mesh Coordinator do?

Agent skill for mesh-coordinator - invoke with $agent-mesh-coordinator. Agent Mesh Coordinator is an agent skill from ruvnet/ruflo.

When should I use Agent Mesh Coordinator?

Agent Mesh Coordinator fits situations like: agent Workflows work in your project.

How do I install Agent Mesh Coordinator in Claude Code?

Run `npx skills add ruvnet/ruflo --skill agent-mesh-coordinator -a claude-code`. Or copy the skill folder (.agents/skills/agent-mesh-coordinator in ruvnet/ruflo) into .claude/skills/agent-mesh-coordinator in your project. Claude Code loads it when a task matches its description.

How do I install Agent Mesh Coordinator in Codex?

Run `npx skills add ruvnet/ruflo --skill agent-mesh-coordinator -a codex`. Or copy the skill folder (.agents/skills/agent-mesh-coordinator in ruvnet/ruflo) into .agents/skills/agent-mesh-coordinator in your project. Codex loads it when a task matches its description.

Can I use Agent Mesh Coordinator in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ruvnet/ruflo --skill agent-mesh-coordinator -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/agent-mesh-coordinator, .gemini/skills/agent-mesh-coordinator, .github/skills/agent-mesh-coordinator and .opencode/skills/agent-mesh-coordinator in your project.

What does Agent Mesh Coordinator need to run?

SKILL.md names no scripts, command-line tools or credentials: Agent Mesh Coordinator is instructions for the agent only. Our summary lists: Python 3.

Does Agent Mesh Coordinator access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Agent Mesh Coordinator safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Agent Mesh Coordinator use?

Agent Mesh Coordinator is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Agent Mesh Coordinator use?

About 3.2k tokens (SKILL.md is roughly 13k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Agent Mesh Coordinator?

Skills that share tags, products or a category with Agent Mesh Coordinator: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 38k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Agent Mesh Coordinator?

ruvnet (a GitHub user) maintains it in ruvnet/ruflo, which has 74,089 GitHub stars. The repository holds 264 skills in this directory. The repository was last updated on October 8, 2026.

Source: ruvnet/ruflo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.