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/storygit 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/commands/jdanigo/hydraia/story)<a href="https://agentmods.dev/commands/jdanigo/hydraia/story"><img src="https://agentmods.dev/badge/commands/jdanigo/hydraia/story.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.1 | $0.00022 | $0.00352 |
| Opus 5 | $0.00011 | $0.00176 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
story 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 6d 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 user story. Run: the story-analysis skill first (interactive PO pass — INVEST check, ambiguity questions one at a time, numbered acceptance criteria → story artifact under docs/hydraia/stories/), then Phases 0-3: context, think gate, design + threat model (the spec references the ACs by number), and the detailed plan with its self-review loop, including the qa-functional dispatch (Given/When/Then cases + traceability matrix under docs/hydraia/qa/). All artifact paths are relative to the resolved artifacts base — the external dir when chosen at the storage gate. Then STOP — do not execute.
Produce ALL FOUR artifacts: story artifact, design spec, QA case document, and the frozen plan. Do NOT arm the spec-drive gate and do NOT write feature code — this is the human review point before implementation. Run /hydraia:feature when ready to build.
Request: $ARGUMENTS
When finished, record telemetry for this run: printf 'brief\n' > <base>/.run-complete (where <base> is the artifacts dir resolved at the storage gate — docs/hydraia/ by default, or the external dir if chosen). The Stop hook logs this run's real token/model/sub-agent usage to the local dashboard (delta-scoped per session, so it never double-counts). Do not hand-write the numbers.
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.
- 6d ago First seen · 13 lines · 22 tokens per session scan A 742db47033d3
story is a command published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 16d ago), licensed MIT. It adds 22 tokens to every session and 352 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.
critique-screen
Run all seven visual critiques on a screen and output a prioritised fix list.
plan
Create a structured task-by-task implementation plan for a feature and write it to docs/superpowers/plans/.
diff-script
Compare an MDL script against the project's current state.
toh-help
Display all Toh Framework commands and quick usage guide.
dashboard-session-diff
Show file changes (git diff) for a session by id-prefix. Usage /dashboard:session-diff . Runs locally, no LLM.