Verified Agent Skill record

hivemind

Hivemind is an orchestration layer that lets Claude Code delegate work to opencode workers, either individually or in isolated parallel swarms. It includes worker invocation, progress tracking, aggregation, benchmarking, slash-command patterns, and fallback guidance.

Tasks

Delegate a read-only question or small task to one opencode worker through scripts/oc-worker.mjs.
Decompose a larger task into 2–5 independent subtasks, run writing workers in isolated git worktrees, review each diff, merge approved branches, remove worktrees, and run tests.
Run the documented benchmark configurations for a repository and task, then record and review the generated benchmark results.
Use the bundled fleet patterns for parallel review, research, migration, or test work when their documented command and isolation requirements fit the task.

Inputs

A task description supplied as TASK TEXT to scripts/oc-worker.mjs or a bundled slash command.
For worker execution, optional documented values for --agent, --dir, --model, --timeout, --run, and --label.
For benchmarking, a repository path and optional configurations and task number.
For fleet commands, the documented task, question, diff, target, or migration input.

Outputs

A single compact JSON line from oc-worker.mjs containing worker status and, on success, result, token counts, cost, duration, label, agent, and model.
Failure JSON containing ok:false, a documented stage, and an error.
For runs using --run and --label, lifecycle events appended to a .runs/<id>.jsonl file.
For benchmarking, JSONL records appended to bench-results.jsonl.
Reviewed diffs, merged approved branches, and test results when using the swarm workflow.

Limitations and checks

The skill depends on the third-party opencode CLI and does not bundle it.
Free-tier availability, rate limits, and pricing may change; heavy swarms can receive 429 responses.
Worker quality varies, so worker outputs and diffs require review.
Benchmark configuration C consumes real Claude tokens for orchestration.
Worker traffic goes to opencode endpoints; secrets, credentials, and private code should not be delegated.
The documented installation does not establish platform support beyond the stated Windows notes.
Before delegation, confirm that opencode is installed on PATH and that the opencode account is authenticated.
For every writing worker, verify that an isolated git worktree was created before the worker is started.