Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By AR6420
Route complex software engineering tasks to specialized Haiku/Sonnet subagents orchestrated by a managing agent, reducing API costs by ~50% while automating code review, security scanning, git operations, environment preflights, dependency analysis, documentation, and testing.
npx claudepluginhub ar6420/hail_hydraShow current Hydra configuration and how to customize it
Manually run the Hydra security and quality scan on specified files or directories
Show all available Hydra commands, agents, and a quick reference guide
View, rebuild, or query the codebase dependency map
Run two-phase environment and compatibility check before starting a new project build
🔵 Hydra's analysis head — thorough code review, debugging, and analysis agent. Use PROACTIVELY whenever Claude needs to review code for quality, analyze a bug with error messages or stack traces, evaluate dependencies, assess test coverage, review pull request changes, identify performance issues, or analyze technical debt. Runs on Sonnet for strong reasoning at good speed. May run in parallel with other Hydra agents — produces self-contained, clearly structured output so the orchestrator can merge results from multiple simultaneous agents.
🔵 Hydra's implementation head — capable code writing and engineering agent. Use PROACTIVELY whenever Claude needs to write new code, implement features, refactor existing code, create or modify tests, fix bugs with clear error messages, make API integrations, or perform any code writing task that follows well-understood patterns. Runs on Sonnet for a strong balance of speed and capability. Use this for all standard implementation work — reserve Opus only for novel architecture or extremely subtle debugging. May run in parallel with other Hydra agents — produces self-contained, clearly structured output so the orchestrator can merge results from multiple simultaneous agents.
🟢 Hydra's git operations specialist. Handles all version control tasks: staging, committing with well-crafted Conventional Commits messages, branching, merging, rebasing, stashing, cherry-picking, log inspection, diff analysis, and conflict detection. Runs on Haiku — git operations are mechanical and well-defined. Use hydra-analyst for merge conflict RESOLUTION (requires code comprehension) but hydra-git for conflict DETECTION and all other git operations. May run in parallel with other Hydra agents — produces self-contained, clearly structured output so the orchestrator can merge results from multiple simultaneous agents.
🟢 Hydra's security and quality gate agent. Automatically invoked after hydra-coder (Sonnet) produces code changes. Performs a fast scan for common security issues (hardcoded secrets, SQL injection, XSS, unsafe deserialization, exposed API keys), code quality checks (unused imports, dead code, missing error handling on async operations), and leftover debug artifacts (console.log, TODO/FIXME/HACK comments). Runs on Haiku for speed — this is a fast gate, not a deep audit. For deep security review, use hydra-analyst instead. May run in parallel with other Hydra agents — produces self-contained, clearly structured output so the orchestrator can merge results from multiple simultaneous agents.
Environment and dependency preflight check for new projects. Detects runtime versions, runs compatibility probe scripts, collects the full dependency tree, and returns a structured inventory for cross-component analysis. Use when the user runs /hydra:preflight or when starting work on a new or unfamiliar project.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This skill should be used when the model's ROLE_TYPE is orchestrator and needs to delegate tasks to specialist sub-agents. Provides scientific delegation framework ensuring world-building context (WHERE, WHAT, WHY) while preserving agent autonomy in implementation decisions (HOW). Use when planning task delegation, structuring sub-agent prompts, or coordinating multi-agent workflows.
Agent orchestration harness for Claude Code — campaign persistence, fleet coordination, intent routing
Multi-agent /workflow development pipeline (planner → plan-review → coder → code-review) with typed handoff contracts, lifecycle hooks, and MCP servers.
Repowire mesh usage skills for AI coding agents: cross-agent review and planning, delegate, usage patterns, and install/update. Backend-agnostic and parameterised on the agent you choose.
HelloAGENTS — The orchestration kernel that makes any AI CLI smarter. Adds intelligent routing, unified QA gates, safety guards, and notifications.
OpenAgentsControl — multi-agent orchestration for Claude Code. Context-aware development with skills, subagents, parallel execution, and automated code review.
Multi-Headed Speculative Execution for Claude Code
"Cut off one head, two more shall take its place."
Except here — every head is doing your work faster and cheaper.
10 agents · 12 slash commands · 4 hooks · Codebase map · Real token tracking · Persistent memory
Hydra is a curated multi-agent toolkit for Claude Code. It ships 10 specialized agents pinned to cost-effective models (Haiku and Sonnet), 12 slash commands for direct invocation, and one automatic touchpoint that recommends integration verification after substantial code changes.
Each agent runs on the smallest model that can do its job well. When invoked, Hydra typically reduces per-task cost by 40–60% compared to running the same work on the orchestrator alone — while maintaining output quality through verification.
Think of it this way:
Would you hire a $500/hr architect to carry bricks? No. You'd have them design the building and let the crew handle construction. That's the model Hydra follows when you invoke a specialized head.
New in v2.0.0: Every agent has persistent memory — they learn your codebase patterns, conventions, and architectural decisions across sessions. The orchestrator (Opus) also maintains its own memory of fragile zones and routing decisions. The hydra-sentinel workflow catches integration breakage after substantial code changes — and code isn't presented to you until verification completes.
New in v2.1.0: The Codebase Map gives every agent instant access to file dependencies, blast radius, risk scores, and test coverage — replacing slow grep-based scanning with instant JSON lookups. Sentinel is now 3–5× faster and 3–5× cheaper per scan.
New in v2.3.2 — Internal Compression: Subagents now run with compressed INTERNAL thinking, not just compressed final output. The intermediate prose ("Let me check…", "I'll examine…", "Now I'll trace…") that no one ever reads is drastically reduced — ~40–60% fewer billed tokens per subagent dispatch, with no change to the final output Opus receives. The new /hydra:stfu skill extends this compression to ALL subagents in a session — Hydra's own, third-party, and Claude Code's built-in agents. Session-scoped, runtime-only, no file modifications. Activate via /hydra:stfu; deactivate via /skills.
New in v2.4.0 — Toolkit Repositioning: SKILL.md refocused to the toolkit-with-touchpoints model. The hydra-auto-guard hook now injects a sentinel verification directive after substantial code changes (new files, MultiEdit batches, or edits affecting more than ~5 lines). Trivial edits stay silent. /hydra:stats shows actionable guidance when no Hydra dispatches occurred in the session instead of empty zeros.
Hydra's biggest cost savings come from explicit invocation in scenarios where specialized handling genuinely helps: