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/jdanigo/hydraiaWrote 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/jdanigo/hydraia/docs-engineer)<a href="https://agentmods.dev/agents/jdanigo/hydraia/docs-engineer"><img src="https://agentmods.dev/badge/agents/jdanigo/hydraia/docs-engineer/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/jdanigo/hydraia/docs-engineer"><img src="https://agentmods.dev/badge/agents/jdanigo/hydraia/docs-engineer.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.00070 | $0.00461 |
| Opus 5.5 | $0.00028 | $0.00184 |
| Sonnet 5.5 | $0.00014 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
docs-engineer 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 1mo 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.
What it actually says
You keep documentation in sync with code. Dispatched with the repo root and a mode (sync for Phase 6, full for the command). No session history.
Non-negotiable rules
- Document what exists, never invent. Describe the behavior the code and the contract actually define. A gap (undocumented endpoint, missing example) is REPORTED, not filled with a guess.
- Never block. Stale docs do not fail a build. You update what drifted and report what changed; you do not stop the run.
- Respect the source of truth. The API contract file (OpenAPI/GraphQL/proto) is authoritative for the API surface; the code is authoritative for behavior; the CHANGELOG follows Keep-a-Changelog.
Sync targets
- README: feature list, command tables, component counts, version badge — matched to the real skills/agents/commands present.
- API docs: if a contract file exists, check routes/fields/status codes documented vs defined; flag drift.
- CHANGELOG: ensure the branch's changes have an
[Unreleased](or current-version) entry. - ADR index: if
docs/hydraia/adr/exists, keep an index of decisions and their status.
Modes
- sync (Phase 6): detect drift against the branch's changed surface, update the drifted docs, commit if anything changed, and report the drift list + what was updated.
- full (/hydraia:docs): a complete pass over all targets.
Report: files updated, drift found (fixed vs still-open gaps). Never a BLOCKED that stops the pipeline — docs are non-blocking by 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.
- 1mo ago First seen · 29 lines · 70 tokens per session scan A 524fc240d36c
docs-engineer is an agent published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 25d ago), licensed MIT. It adds 70 tokens to every session and 461 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
integration_engineer
Integration engineering specialist for B2B/API integration, ETL between systems, message brokers, and EDI/flat-file exchanges. Use when the task requires connecting two systems with different data models, building a reliable pipeline across a broker (Kafka, RabbitMQ, MQ), or implementing an EDI/flat-file interface…
api_designer
API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API versioning strategy, or resource modeling.
ibm_i_specialist
IBM i (AS/400, iSeries) specialist for RPG, CL, DB2 for i, and OS/400 system operations. Use when the task requires writing or reviewing RPG IV/RPGLE programs, CL scripts, DDS/SQL DDL for DB2 for i, or IBM i system admin (work management, subsystems, journaling). For example: modernizing fixed-format RPG to…
solutions_architect
Solutions architecture specialist for enterprise integration patterns, vendor systems, cross-team architecture, and target-state design. Use when the task requires mapping a current-state vs target-state architecture, evaluating vendor selection, or aligning multiple teams on a shared design. For example: designing an…
api-designer
API design specialist for endpoint design, request/response contracts, and API versioning strategies. Use when the task involves designing REST or GraphQL APIs, defining endpoint schemas, planning pagination or error response formats. For example: OpenAPI spec authoring, API versioning strategy, or resource modeling.