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/preflightgit 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/preflight)<a href="https://agentmods.dev/commands/ar6420/hail_hydra/preflight"><img src="https://agentmods.dev/badge/commands/ar6420/hail_hydra/preflight.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.00757 |
| Opus 5 | $0.00006 | $0.00378 |
| Sonnet 5 | $0.00003 | $0.00151 |
| Haiku 4.5 | $0.00001 | $0.00076 |
Grade A, and why
preflight 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hydra Preflight
Run the two-phase environment and compatibility check before starting work on a new or unfamiliar project. Catches broken GPU stacks, missing env vars, and incompatible dependency pairs before they cost hours of debugging.
Execute the Preflight Protocol
Follow the Preflight Protocol defined in SKILL.md — two phases, always dispatched in sequence. Never skip Phase 2.
Phase 1 — Detection (dispatch hydra-preflight, Haiku 4.5)
Dispatch the hydra-preflight agent with this prompt:
Run a full preflight check on this project. Collect runtime versions, run all
GPU/CUDA probe scripts, inventory installed packages, compare .env.example
against .env, verify build tools exist, and check service connectivity. Return
the full structured PREFLIGHT_INVENTORY JSON. Do not make recommendations.
Wait for the agent to return PREFLIGHT_INVENTORY_COMPLETE before proceeding.
Phase 2 — Analysis (dispatch hydra-analyst, Sonnet 4.6)
Pass the full PREFLIGHT_INVENTORY from Phase 1 as context and dispatch
hydra-analyst with this prompt:
You are performing a compatibility analysis on the following environment inventory.
Cross-reference all detected versions against known compatibility matrices.
Pay special attention to GPU stack combinations (PyTorch/CUDA/cuDNN),
framework pairs (React/Next, Python/TF), and Node/native addon combinations.
For each component or pair, return one of three verdicts:
✅ COMPATIBLE — versions are known-good together
⚠️ KNOWN RISK — this combination has known issues or is untested
❌ CONFIRMED BREAK — probe output or known matrix confirms incompatibility
For ❌ verdicts, include the specific fix (e.g. "pin pytorch==2.7.0").
For ⚠️ verdicts, include what to watch for.
For unknowns, flag as "UNVERIFIED — test before building" rather than assuming green.
Probe output from Phase 1 is ground truth — it always beats matrix knowledge.
If torch.cuda.is_available() returned False, that is a ❌ regardless of what
the version matrix says.
INVENTORY:
[paste full PREFLIGHT_INVENTORY here]
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 · 95 lines · 13 tokens per session scan A 41a31b2268c7
preflight is a command published in the GitHub repository AR6420/Hail_Hydra (48 stars, last pushed 24d ago), licensed MIT. It adds 13 tokens to every session and 757 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.