agenthub

Spawns parallel AI agents in isolated git worktrees to compete on tasks and merges the winning branch.

Updated Aug 14, 2026
One-click install
npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill agenthub-rohithdgrr
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agenthub
Source: https://github.com/Rohithdgrr/REEK-uninstaller/tree/main/.opencode/skills/agenthub
Command: npx skills add https://github.com/Rohithdgrr/REEK-uninstaller --skill agenthub-rohithdgrr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Trying multiple solution approaches to a coding or content task sequentially is slow, and comparing alternatives manually is error-prone. This Skill runs N parallel agents on the same task in isolated git worktrees, evaluates their results by metric or LLM judge, and merges the best branch automatically. ## Core Features & Use Cases - Parallel agent competition: Spawn N subagents in isolated git worktrees, each working independently on the same task with no cross-communication. - Flexible evaluation: Rank results by numeric metrics (latency, coverage, size), LLM-judged quality, or a hybrid of both, then merge the winner with git merge --no-ff and archive losers as tags. - Predefined agent templates: Built-in templates for optimizer, refactorer, test-writer, and bug-fixer patterns, each with a structured iteration loop and strategy assignment. - Use Case: You want to reduce API response time below 100ms. Initialize a session with 3 agents, each assigned a different strategy (caching, algorithm optimization, I/O batching), let them iterate in parallel worktrees, then rank by p50_ms and merge the winner. ## Quick Start Ask the assistant to initialize an AgentHub session with your task description and agent count, then spawn the agents and evaluate their results.

Frequently Asked Questions about agenthub

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run multiple AI agents in parallel on the same coding task?▼

Initialize a session with hub_init.py specifying the task and agent count, then spawn agents via the /hub:spawn command. Each agent works in an isolated git worktree, and results are ranked by metric or LLM judge before merging the winning branch.

How do I compare different solutions to the same problem with git worktrees?▼

Create a separate git worktree per approach so each solution develops on its own branch without conflicts. AgentHub automates this by spawning agents with worktree isolation, then ranking branches by an eval command or diff quality.

Does AgentHub require a git repository to work?▼

Yes, AgentHub requires a git repository because it relies on git worktrees for agent isolation and git branches for tracking each agent's attempts. The hub_init.py script validates the repository before creating a session.

How are agent results evaluated and ranked?▼

Results are ranked by metric mode, which runs an eval command in each worktree and parses a numeric value, or by LLM judge mode, where the coordinator reads diffs and ranks by correctness, simplicity, and quality. A hybrid mode uses metrics first and LLM judging for close ties.

What happens to losing agent branches after a merge?▼

Losing branches are archived as immutable git tags under hub/archive/{session}/agent-{N} before their branch refs are deleted. This preserves every approach in the DAG while keeping the branch list clean, and worktrees are removed during cleanup.

When should I not use parallel multi-agent competition?▼

Avoid it for simple single-approach tasks where one agent suffices, since coordination overhead outweighs benefits. Beyond 5 agents, diminishing returns set in for most tasks, and evaluation cost increases with each additional agent.