Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/ar6420/hail_hydra/updategit clone --depth 1 https://github.com/AR6420/Hail_HydraWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/ar6420/hail_hydra/update)<a href="https://agentmods.dev/commands/ar6420/hail_hydra/update"><img src="https://agentmods.dev/badge/commands/ar6420/hail_hydra/update.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00010 | $0.00510 |
| Opus 5 | $0.00005 | $0.00255 |
| Sonnet 5 | $0.00002 | $0.00102 |
| Haiku 4.5 | $0.00001 | $0.00051 |
Grade A, and why
update scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 4d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sL "https://raw.githubusercontent.com/AR6420/Hail_Hydra/main/CHANGELOG.md" What it actually says
Hydra Update
Run the following steps to update Hydra to the latest version:
Step 1 — Check versions
cat ~/.claude/skills/hydra/VERSION 2>/dev/null || echo "VERSION file not found"
npm view hail-hydra-cc version 2>/dev/null || echo "Package not found on npm"
If the installed version matches the latest npm version, tell the user: "🐉 Hydra is already at the latest version ([version])." and stop here.
Step 2 — Show changelog preview
Fetch the CHANGELOG from GitHub:
curl -sL "https://raw.githubusercontent.com/AR6420/Hail_Hydra/main/CHANGELOG.md"
Parse the changelog to extract entries between the installed version and the latest version. Display a formatted "What's New" section:
🐉 Hydra Update Available: [installed] → [latest]
═══════════════════════════════════════════════════
📋 What's New:
[changelog entries for versions between installed and latest]
If the changelog fetch fails, skip the preview and continue with the update.
Step 3 — Show safety note
Display:
⚠️ What gets replaced:
• Agent definitions (agents/*.md)
• SKILL.md, references, commands, hooks
• VERSION file
✅ What's preserved:
• Your hydra.config.md settings
• Agent memory directories (memory/)
• CLAUDE.md orchestrator notes
• settings.json hook registrations (re-registered automatically)
Step 4 — Ask for confirmation
Ask the user: "Proceed with update? [Y/n]"
If they decline, respond: "🐉 Update cancelled." and stop.
Step 5 — Run the update
npx hail-hydra-cc@latest --global
Step 6 — Verify
cat ~/.claude/skills/hydra/VERSION
Report to the user:
- If updated: "🐉 Hydra updated from [old] → [new]. All heads refreshed. Restart Claude Code to load the new files."
- If error: Show the error and suggest running
npx hail-hydra-cc@latest --globalmanually in their terminal.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 4d ago First seen · 79 lines · 10 tokens per session scan A a4cf61ee028c
update is a command published in the GitHub repository AR6420/Hail_Hydra (48 stars, last pushed 23d ago), licensed MIT. It adds 10 tokens to every session and 510 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
install-context
Install OpenAgents Control context files.
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
health
Run documentation health checks (freshness, links, drift, cross-doc consistency).
tidy
Consistency check for non-code repos with INDEX.md hierarchy. Verifies INDEX.md accuracy, MEMORY.md references, orphaned files, stale dates, and WAITING markers.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…
batch-execute
Execute a batch of ops plans continuously without user input, storing any issues and user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.