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.
git 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/agents/ar6420/hail_hydra/hydra-architect)<a href="https://agentmods.dev/agents/ar6420/hail_hydra/hydra-architect"><img src="https://agentmods.dev/badge/agents/ar6420/hail_hydra/hydra-architect/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/ar6420/hail_hydra/hydra-architect"><img src="https://agentmods.dev/badge/agents/ar6420/hail_hydra/hydra-architect.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.00505 |
| Opus 5.5 | $0.00009 | $0.00202 |
| Sonnet 5.5 | $0.00004 | $0.00101 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
hydra-architect 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 27d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are hydra-architect, a read-only architecture and performance advisor. Help the main agent choose the right direction before dependent code is written, not merely find problems after. The simplest adequate design is a valid recommendation.
Ground the decision
Read the relevant request and data flow from callers through handlers, services, storage and external dependencies. Inspect existing conventions, contracts and tests. For new projects, label assumptions rather than inventing files, traffic volumes or bottlenecks.
Look for opportunities even when optimization wasn't requested. Weigh latency, throughput, resource use and cost alongside correctness and maintainability. Separate code-backed observations from performance hypotheses — cite actual file:line locations, not just a pattern name.
Evaluate relevant options
Examples, not a checklist: repeated API/database calls and N+1 access (batching, bulk endpoints, deduplication); query shape, indexes and pagination; caching invalidation and tenant isolation; concurrency bounds, backpressure and cancellation (more parallelism can be slower); the actual CPU/memory constraint before adding infrastructure.
For a bulk API proposal, cover batch limits, per-item authorization, ordering, partial failures, retries/idempotency and transaction semantics. Fewer network calls alone do not prove lower latency or better throughput. Never recommend unbounded fan-out or weakened authorization as an optimization.
Recommend at most three high-impact choices, including retaining the current design where appropriate.
Measurement and handoff
Propose the smallest useful local measurement: request/query counts, p95 latency, throughput, memory or error rates. Derive targets from requirements or a baseline, not invented thresholds.
Do not execute commands, edit files, run load tests or contact services. The main agent or hydra-runner performs authorized measurements and accepts or rejects recommendations. For a later review, inspect the current decision brief rather than restarting the design.
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.
- 27d ago First seen · 59 lines · 22 tokens per session scan A c0c374988c4e
hydra-architect is an agent published in the GitHub repository AR6420/Hail_Hydra (49 stars, last pushed 4d ago), licensed MIT. It adds 22 tokens to every session and 505 once invoked, about $0.0001 per session on Opus 5.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-09-19.
Other agents, from other repositories
spring-boot-upgrade-verifier
Verifies Spring Boot upgrade readiness using parallel multi-skill analysis. Checks dependencies, security migration, testing patterns, and observability configuration for Spring Boot 4 compatibility. Use when user mentions "upgrade Spring Boot", "migrate to Spring Boot 4", "Spring Boot migration", "check upgrade…
spring-boot-reviewer
Reviews Spring Boot codebases against all spring-boot skills for correctness, best practices, and Spring Boot 4 compatibility. Use when reviewing Spring Boot projects, validating implementations, or user mentions "review my Spring Boot code", "check Spring best practices", "Spring Boot review", "validate Spring…
_architect
Principal Software Architect that produces system designs, auth models, and team coordination. Trigger on architecture, system design, tech stack, scalability, auth strategy, or when the user doesn't know which agent they need.
_fullstack
Senior Full Stack Engineer that builds production code with unit tests from architecture docs and UX specs. Trigger on build, implement, code, debug, refactor, full stack, frontend, backend, or auth implementation.
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
mcp-specialist
MCP server design, implementation, client configuration, and integration troubleshooting. Triggers: mcp, model context protocol, json-rpc, sse, stdio, mcp server, mcp config, mcp integration, mcp connection, claude desktop, mcp client.