Hive Mind
Spin up queen-led, fault-tolerant multi-agent swarms with claude-flow when several agents must agree under real coordination load.
Overview
Hive-Mind is an agent skill for the Build phase that configures Byzantine fault-tolerant consensus and queen-led swarm coordination for multi-agent distributed tasks through claude-flow.
Install
npx skills add https://github.com/ruvnet/ruflo --skill hive-mindWhat is this skill?
- Documents four swarm topologies: hierarchical, mesh, hierarchical-mesh (recommended for complex work), and adaptive auto
- Maps five consensus strategies with fault tolerance: byzantine (f < n/3), raft, gossip, crdt, and quorum
- Queen-led hierarchical default aimed at anti-drift coordination across workers
- CLI entrypoints via `npx claude-flow hive-mind init` and `hive-mind spawn` with role and topology flags
- Explicit skip guidance for single-agent, local-only, or simple one-shot work
- 4 documented swarm topologies
- 5 documented consensus strategies
Adoption & trust: 637 installs on skills.sh; 58.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You are running several agents in parallel but lack a documented topology and consensus strategy when some nodes fail or drift from the shared goal.
Who is it for?
Multi-agent claude-flow workflows that need hierarchical-mesh coordination, explicit consensus choice, and fault-tolerant distributed operations.
Skip if: Single-agent coding sessions, simple local edits, or tasks with no need for collective multi-agent decision making.
When should I use this skill?
Distributed coordination, fault-tolerant operations, multi-agent consensus, or collective decision making across agents.
What do I get? / Deliverables
You initialize a hive-mind topology, spawn queen/worker roles, and lock in a consensus mode so collective decisions stay consistent under partial failures.
- Initialized hive-mind cluster configuration (topology + consensus flags)
- Spawned queen/worker roles ready for coordinated distributed tasks
Recommended Skills
Journey fit
Hive-Mind configures distributed agent runtime topology and consensus—work you do while standing up multi-agent product infrastructure, not while polishing launch copy. Agent-tooling is the canonical shelf for swarm init, topology choice, and consensus strategy wiring before agents run collective tasks.
How it compares
Use for distributed swarm consensus and coordination CLIs, not for markdown implementation plans or SKILL.md authoring.
Common Questions / FAQ
Who is hive-mind for?
Indie builders and small teams orchestrating multiple AI agents with claude-flow who need structured topologies and consensus instead of fragile peer-to-peer prompting.
When should I use hive-mind?
Use it during Build agent-tooling when you have multi-agent distributed tasks, need fault-tolerant operations, or must reach collective decisions across workers; skip it for single-agent local work.
Is hive-mind safe to install?
Review the Security Audits panel on this Prism page and treat hive-mind as infrastructure that runs shell commands and network-backed coordination—limit credentials and scope before init.
SKILL.md
READMESKILL.md - Hive Mind
# Hive-Mind Skill ## Purpose Byzantine fault-tolerant consensus and distributed swarm coordination. ## When to Trigger - Multi-agent distributed tasks - Fault-tolerant operations needed - Collective decision making - Complex coordination patterns ## Topologies | Topology | Description | Use Case | |----------|-------------|----------| | `hierarchical` | Queen controls workers | Default, anti-drift | | `mesh` | Fully connected peers | Research, exploration | | `hierarchical-mesh` | Hybrid | Recommended for complex | | `adaptive` | Dynamic based on load | Auto-scaling | ## Consensus Strategies | Strategy | Tolerance | Use Case | |----------|-----------|----------| | `byzantine` | f < n/3 faulty | Untrusted environment | | `raft` | f < n/2 faulty | Leader-based, consistent | | `gossip` | Eventual | Large scale, availability | | `crdt` | Conflict-free | Concurrent updates | | `quorum` | Configurable | Tunable consistency | ## Commands ### Initialize Hive-Mind ```bash npx claude-flow hive-mind init --topology hierarchical-mesh --consensus raft ``` ### Spawn Queen ```bash npx claude-flow hive-mind spawn --role queen --name coordinator ``` ### Check Consensus Status ```bash npx claude-flow hive-mind consensus --status ``` ### View Sessions ```bash npx claude-flow hive-mind sessions --active ``` ## Best Practices 1. Use hierarchical for coding tasks (anti-drift) 2. Use raft consensus for consistency 3. Keep agent count under 8 for coordination 4. Run frequent checkpoints