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 instructions/saadnvd1/hydra/claude-mdgit clone --depth 1 https://github.com/saadnvd1/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/instructions/saadnvd1/hydra/claude-md)<a href="https://agentmods.dev/instructions/saadnvd1/hydra/claude-md"><img src="https://agentmods.dev/badge/instructions/saadnvd1/hydra/claude-md.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.00625 | $0.00625 |
| Opus 5 | $0.00313 | $0.00313 |
| Sonnet 5 | $0.00125 | $0.00125 |
| Haiku 4.5 | $0.00063 | $0.00063 |
Grade A, and why
hydra CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-cli
Go CLI. PTY-based wrapper around AI coding CLIs with automatic limit detection and provider switching.
Structure
main.go— entry point, arg routing,ai switch(SIGUSR1 to all PIDs), clipboard helperinternal/config/— YAML config loading, default limit patterns from real CLI sourceinternal/proxy/— PTY proxy: spawns CLI in pseudo-terminal, monitors output, SIGUSR1/SIGQUIT signal handling, provider picker menu (raw mode single-keypress), multi-PID managementinternal/session/— session persistence, Claude Code JSONL session file extraction (~/.claude/projects/<project>/<id>.jsonl), git diff/log capture, continuation prompt builderinternal/logger/— append-only log filetest/— fake provider scripts for testing limit detection flow
Build
go build -o /usr/local/bin/ai .
Config
~/.config/ai-cli/config.yaml — provider chain, permission bypass args/env, limit patterns.
Key Design
- Full PTY passthrough — user sees actual TUI, no filtering
- Output ring buffer (8KB) scanned for limit patterns (ANSI-stripped via regex)
ai switchsends SIGUSR1 to ALL runningaiprocesses via PID files in~/.local/share/ai-cli/pids/- Context extraction reads Claude Code JSONL session files directly, parses user/assistant messages
- Extra CLI args only forwarded to initial provider, not fallbacks (prevents flag leakage)
- Provider picker uses raw mode for single-keypress selection
- Permission bypass baked into config per provider (different mechanisms: CLI flags for Claude/Codex, env var for OpenCode, none needed for Pi)
Provider-Specific Notes
- Claude Code:
--dangerously-skip-permissionsflag. Sessions stored as JSONL at~/.claude/projects/ - OpenCode:
OPENCODE_PERMISSION='{"*":"allow"}'env var (TUI doesn't support--dangerously-skip-permissions, onlyopencode rundoes). Model format:provider/model(e.g.google/gemini-2.5-flash) - Codex:
--full-autoflag. Model format: just model name (e.g.o3) - Pi: No permission system. Model format: pattern match without provider prefix (e.g.
gemini-2.5-flash). Binary requires full nvm path in config due to lazy-loaded nvm.
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 · 41 lines · 625 tokens per session scan A e5d9d595e488
hydra CLAUDE.md is an instructions file published in the GitHub repository saadnvd1/hydra (18 stars, last pushed 4mo ago), licensed MIT. It adds 625 tokens to every session, about $0.0031 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 instructions, from other repositories
crystal CLAUDE.md
Instructions for stravu/crystal, covering crystal - multi-session claude code manager, project overview, references, implementation status: ✅ complete and ✅ implemented features.
easy-cheese python.instructions.md
Instructions for paulnsorensen/easy-cheese, covering hard rules, what to flag and what not to flag.
plan-forge database.instructions.md
Database patterns for .NET — Dapper/EF Core, parameterized queries, migration strategy.
plan-forge naming.instructions.md
Azure naming conventions — Microsoft CAF abbreviations, constraints, uniqueness, tagging.
claude-bridge AGENTS.md
Instructions for kadaba/claude-bridge, covering agents.md — using claude-bridge from any ai coding cli, two independent channels, 1. coordination (the conversation), 2. file transfer (the bytes) — same for every tool and workflows.
AmbyKit CLAUDE.md
Instructions for ambystechcom/AmbyKit, covering claude code — notes for the ambykit repo and claude-specific.