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/helpgit 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/help)<a href="https://agentmods.dev/commands/ar6420/hail_hydra/help"><img src="https://agentmods.dev/badge/commands/ar6420/hail_hydra/help.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.00013 | $0.00575 |
| Opus 5 | $0.00006 | $0.00287 |
| Sonnet 5 | $0.00003 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
help scanned grade A with 0 findings 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
Hydra Help
Display the following help reference directly — do NOT search files or run commands:
🐉 Hydra Framework — Quick Reference
═══════════════════════════════════════
COMMANDS
/hydra:help Show this help screen
/hydra:status Show installed agents, version, config
/hydra:update Update Hydra to the latest version
/hydra:guard Run security scan on files (usage: /hydra:guard src/auth.py)
/hydra:quiet Suppress dispatch logs for this session
/hydra:map View, rebuild, or query the codebase map
/hydra:report Report a bug, request a feature, or share feedback
/hydra:preflight Two-phase environment & compatibility check before new projects
/hydra:stats Show real token usage and estimated savings (no AI estimation)
/hydra:stfu Silence intermediate prose from every dispatched subagent
AGENTS
🟢 hydra-scout (cheap tier) — Explore codebase, find files, map structure
🟢 hydra-runner (cheap tier) — Run tests, linters, build commands
🟢 hydra-scribe (cheap tier) — Write docs, comments, READMEs
🟢 hydra-guard (cheap tier) — Security scan, quality gate
🟢 hydra-git (cheap tier) — Git operations, commits, branches
🟢 hydra-preflight (cheap tier) — Environment detection, version probing, dep inventory
🟢 hydra-sentinel-scan (cheap tier) — Fast integration sweep after code changes
🔵 hydra-coder (mid tier) — Write and edit code
🔵 hydra-analyst (mid tier) — Debug, diagnose, review
🔵 hydra-sentinel (mid tier) — Deep integration analysis (when scan flags issues)
The concrete model behind each tier depends on the host CLI you installed on.
HOW IT WORKS
The orchestrator automatically delegates tasks to cheaper, faster
agents in the cheap and mid tiers — saving ~50% on API costs while
the orchestrator verifies quality.
You don't need to do anything. Just work normally.
Hydra operates invisibly unless you check the dispatch log.
LINKS
GitHub: https://github.com/AR6420/Hail_Hydra
npm: https://www.npmjs.com/package/hail-hydra-cc
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 · 50 lines · 13 tokens per session scan A 1bf3345c8426
help is a command published in the GitHub repository AR6420/Hail_Hydra (48 stars, last pushed 23d ago), licensed MIT. It adds 13 tokens to every session and 575 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. 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.