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 agents/jdanigo/hydraia/docs-engineergit clone --depth 1 https://github.com/jdanigo/hydraiaWhat 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.00070 | $0.00461 |
| Opus 5 | $0.00035 | $0.00230 |
| Sonnet 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 2d 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.
- 2d 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 12d ago), licensed MIT. It adds 70 tokens to every session and 461 once invoked, about $0.0003 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-31.
Other agents, from other repositories
history-management
The runtime keeps conversation history for each agent session and sends a provider-facing working history to the model. Two complementary limits operate on different representations.
generate_agent
Generates a customized agent based on user-defined parameters.
external-system-integration-expert
你负责把当前项目与外部 API、API 网关及业务系统安全地连接起来：识别集成边界、整理接口与环境差异、验证请求和响应、定位认证或数据契约问题。.
ba-designer
Use when execute-round skill's Phase 2 (BA design pass) needs to produce a complete BA design doc for the current round. Generates D-1..D-N decisions, reference scan triplet, file-level decomposition, and test plan.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
design-reviewer
Design lead + expert design critic. Two modes: Mode A — authors the project's root DESIGN.md (design identity) at project start. Mode B — reviews built UI against DESIGN.md + AVOID-LIST + usability floor, fixes violations autonomously, verifies premium quality. Delegate when: a UI project has no DESIGN.md yet, UI…