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 skills add jdanigo/hydraia --skill story-analysisgit 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/skills/jdanigo/hydraia/story-analysis)<a href="https://agentmods.dev/skills/jdanigo/hydraia/story-analysis"><img src="https://agentmods.dev/badge/skills/jdanigo/hydraia/story-analysis/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/skills/jdanigo/hydraia/story-analysis"><img src="https://agentmods.dev/badge/skills/jdanigo/hydraia/story-analysis.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.00056 | $0.00740 |
| Opus 5.5 | $0.00022 | $0.00296 |
| Sonnet 5.5 | $0.00011 | $0.00148 |
| Haiku 4.5 | $0.00006 | $0.00074 |
Grade A, and why
story-analysis 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.
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.
Story Analysis — the Product Owner
Runs in the MAIN session (the interactive half of the Hydraia pipeline — pausing to ask is correct here). Turns a raw user story into a refined story artifact with numbered acceptance criteria that Phase 2 (design) consumes.
Flow
- Ingest. Accept the story as inline text, a file path, or a PDF (convert PDFs with markitdown per Phase 0 rules — never raw bytes).
- INVEST check. Score the story letter by letter — Independent, Negotiable, Valuable, Estimable, Small, Testable. Each failing letter becomes a concrete finding to resolve with the human (e.g. fails S → propose a split; fails T → the missing observable outcome becomes a question).
- Epic detection. If the story hides multiple independent deliverables, say so, propose a split into separate stories, and let the human pick the first slice. Record the split decision in the artifact.
- Ambiguity hunt. Undefined terms, missing actors or roles, unstated error paths, implicit assumptions, unowned edge cases. Each becomes ONE question to the human, asked one at a time. Stop when what remains is cosmetic.
- Acceptance criteria. Extract the criteria already present. PROPOSE the missing ones and get explicit confirmation — never silently invent. Number every criterion
AC-1, AC-2, …. Each AC must be independently testable: a QA engineer could write Given/When/Then for it without asking anything. - Write the artifact to
docs/hydraia/stories/YYYY-MM-DD-<slug>.mdusing the template below, and commit it (docs:prefix). - Hand off to Phase 2 (brainstorming) with the artifact as the primary design input. The Phase 2 spec MUST reference acceptance criteria by their AC 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.
- 1mo ago First seen · 59 lines · 56 tokens per session scan A 33306d44b36f
story-analysis is a skill published in the GitHub repository jdanigo/hydraia (8 stars, last pushed 25d ago), licensed MIT. It adds 56 tokens to every session and 740 once invoked, about $0.0002 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-03.
Other skills, from other repositories
pm-tech-spec-review
Review an engineering technical spec through a PM lens — does it cover every PRD requirement, does it preserve user/UX intent, does it quietly add or drop scope, what are the product risks, what's missing for launch. Produces a priority-tagged findings list + clarifying questions for engineering. Use after eng drafts…
deliver-task
Drive one READY task end-to-end — implement in a worktree, independent adversarial review, bounded 3-iteration patch loop, then hand to a human for merge. Pass the issue number, e.g. "/deliver-task 42". A single-command composition of next-task + review-task + patch-task.
01-sdlc
Orchestrates a request from framing to a draft pull request, autonomous or supervised, isolating implementation, independent review, and final outcome challenge. Use when the user wants to deliver a change end to end. Not for one step.
00-async-dev
Drive the async-dev pipeline from one entry point, whether setup, run, or review. Use when the user wants to install async dev, run a ready issue, or address PR review comments, or on a webhook trigger. Not for plain status checks.
great_cto
Use when the CTO describes a feature, task, or project goal. Orchestrates the full SDLC pipeline automatically based on project type.
resume-session
Resume an interrupted Maestro session using the existing active-session file and shared phase tracking.