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/guardgit 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/guard)<a href="https://agentmods.dev/commands/ar6420/hail_hydra/guard"><img src="https://agentmods.dev/badge/commands/ar6420/hail_hydra/guard.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.00014 | $0.00564 |
| Opus 5 | $0.00007 | $0.00282 |
| Sonnet 5 | $0.00003 | $0.00113 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
guard 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hydra Guard — Manual Security Scan
Run a focused security and quality scan on the specified files.
Target: $ARGUMENTS
If no arguments provided, scan all files changed since the last commit:
git diff --name-only HEAD 2>/dev/null || echo "Not a git repository or no changes"
Scan Checklist
For each target file, check for:
CRITICAL (security)
- Hardcoded secrets, API keys, tokens, passwords (patterns:
sk-,ghp_,AKIA,password =,secret =,token =,api_key =) - SQL injection vulnerabilities (string concatenation in queries)
- XSS vulnerabilities (unescaped user input in HTML output)
- Unsafe deserialization (
eval(),pickle.loads(),unserialize()) - Path traversal (
../in file operations without validation) - Command injection (user input passed to shell commands)
WARNING (quality)
console.log/print()debug leftovers- TODO/FIXME/HACK comments
- Unused imports (obvious cases only)
- Missing error handling on async operations (no try/catch, no .catch())
- Empty catch blocks
- Hardcoded URLs or magic numbers without constants
INFO (style)
- Functions longer than 100 lines
- Deeply nested conditionals (3+ levels)
- Inconsistent naming conventions within the same file
Output Format
🐉 Hydra Guard — Security & Quality Report
═══════════════════════════════════════════
Files scanned: 3
🔴 CRITICAL (2 findings)
src/auth.py:45 Hardcoded API key: OPENAI_KEY = "sk-..."
src/db.py:78 SQL injection: f-string in query construction
⚠️ WARNING (3 findings)
src/auth.py:12 console.log left in production code
src/utils.py:89 Empty catch block — errors silently swallowed
src/api.py:34 TODO: "fix this later" (line 34)
ℹ️ INFO (1 finding)
src/handler.py:1 Function process_request is 142 lines long
Summary: 2 critical · 3 warnings · 1 info
If no issues found:
🐉 Hydra Guard — All Clear ✅
Files scanned: 3 | No issues found.
Important: This is a FAST scan, not a deep audit. For thorough security review, use hydra-analyst instead.
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 · 72 lines · 14 tokens per session scan A 7aa50e0b2e2e
guard is a command published in the GitHub repository AR6420/Hail_Hydra (48 stars, last pushed 24d ago), licensed MIT. It adds 14 tokens to every session and 564 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.
p3-data-model
Designs the Data Model with entities and relationships as well as the API design with interface specification. The result is DATAMODEL.md and APISPEC.md as the binding foundation for implementation.