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/statusgit 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/status)<a href="https://agentmods.dev/commands/ar6420/hail_hydra/status"><img src="https://agentmods.dev/badge/commands/ar6420/hail_hydra/status.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.00015 | $0.00890 |
| Opus 5 | $0.00008 | $0.00445 |
| Sonnet 5 | $0.00003 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
status 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hydra Status
Show a comprehensive status report for the Hydra framework.
1. Version Info
INSTALLED=$(cat ~/.claude/skills/hydra/VERSION 2>/dev/null || echo "unknown")
echo "Installed: $INSTALLED"
LATEST=$(npm view hail-hydra-cc version 2>/dev/null || echo "unknown")
echo "Latest: $LATEST"
2. Installed Agents
echo "=== Global Agents ==="
ls -1 ~/.claude/agents/hydra-*.md 2>/dev/null || echo "None found"
echo "=== Local Agents ==="
ls -1 .claude/agents/hydra-*.md 2>/dev/null || echo "None found"
3. Installed Commands
echo "=== Global Commands ==="
ls -1 ~/.claude/commands/hydra/*.md 2>/dev/null || echo "None found"
echo "=== Local Commands ==="
ls -1 .claude/commands/hydra/*.md 2>/dev/null || echo "None found"
4. Hooks
ls -1 ~/.claude/hooks/hydra-*.js 2>/dev/null || echo "None found"
5. Configuration
cat ~/.claude/skills/hydra/config/hydra.config.md 2>/dev/null || \
cat .claude/skills/hydra/config/hydra.config.md 2>/dev/null || \
echo "No config file found (using defaults: mode balanced, dispatch_log on, auto_guard on).
To customize, create ~/.claude/skills/hydra/config/hydra.config.md (or .claude/... for project-level)."
6. Codebase Map
if [ -f ".claude/hydra/codebase-map.json" ]; then
echo "Map: ✅ Exists"
node -e "const m=JSON.parse(require('fs').readFileSync('.claude/hydra/codebase-map.json','utf8'));console.log('Files:',m._meta.file_count);console.log('Built:',m._meta.built_at);console.log('Hash:',m._meta.git_hash);"
else
echo "Map: ❌ Not built yet (run /hydra:map rebuild)"
fi
Display Format
Present results as a clean status card:
🐉 Hydra Framework Status
──────────────────────────────
Version: X.Y.Z (latest: X.Y.Z ✅) OR (update available: X.Y.Z ⚡)
Install: Global (~/.claude/)
Agents (10):
🟢 hydra-scout (cheap tier) ✅
🟢 hydra-runner (cheap tier) ✅
🟢 hydra-scribe (cheap tier) ✅
🟢 hydra-guard (cheap tier) ✅
🟢 hydra-git (cheap tier) ✅
🟢 hydra-preflight (cheap tier) ✅
🟢 hydra-sentinel-scan (cheap tier) ✅
🔵 hydra-coder (mid tier) ✅
🔵 hydra-analyst (mid tier) ✅
🔵 hydra-sentinel (mid tier) ✅
Commands (10): update, status, help, guard, quiet, report, map, preflight, stats, stfu
Hooks (6): check-update ✅, statusline ✅, token-math ✅, auto-guard ✅, notify ✅, sentinel-done ✅
Map: ✅ Current (487 files, built 2026-03-26)
Config: balanced mode, dispatch log on, auto-guard on
──────────────────────────────
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.
- 5d ago First seen · 90 lines · 15 tokens per session scan A 9ef3cd988397
status is a command published in the GitHub repository AR6420/Hail_Hydra (48 stars, last pushed 24d ago), licensed MIT. It adds 15 tokens to every session and 890 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.
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.
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.
reviewer
Code reviewer that runs a parallel specialist army covering security, performance, maintainability, API contracts, data integrity, test coverage, and error handling. Trigger on code review, review, PR review, pull request, or review army.
konzept-update
This command updates an existing rough concept based on new findings, clarified open questions, or changed requirements. Each revision is versioned and timestamped so that the evolution of the concept remains traceable.