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/jdanigo/hydraia/dbgit 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.00027 | $0.00199 |
| Opus 5 | $0.00014 | $0.00100 |
| Sonnet 5 | $0.00005 | $0.00040 |
| Haiku 4.5 | $0.00003 | $0.00020 |
Grade A, and why
db 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
Invoke the hydraia skill forcing the Phase -1 route to performance (DB-shaped). Follow the performance-tuning and db-optimization skills with the db-performance-tuner agent as PRIMARY diagnostician: detect the engine from evidence, collect read-only evidence (EXPLAIN plans, stat views, slow logs — redacting data values), classify findings (index, query shape, N+1, locking, pooling, schema, caching), write the spec with baseline + numeric target, then run the full pipeline. Schema changes follow expand-contract; write-shaped operations are plan tasks, never direct agent actions. Dispatch perf-engineer too only if the evidence points outside the database.
Request: $ARGUMENTS
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 · 9 lines · 27 tokens per session scan A d33d838a3ffe
db is a command published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 13d ago), licensed MIT. It adds 27 tokens to every session and 199 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-31.
Other commands, from other repositories
MIGRATE_DESIGN
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
trex.test.integration
Run integration tests against a real PostgreSQL database (provisioned automatically via testcontainers).
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
pipeline-undo
Undo a pipeline run's result. With worktree isolation (the current engine), this is clean and low-risk: a run never touches your checkout — its result lives only on a pipeline/ branch (and, for a --push run, on the remote). "Undo" therefore means deleting that branch and its worktree, not reverting your working tree.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.