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 arozumenko/sdlc-skills --skill journeys-to-hypothesesgit clone --depth 1 https://github.com/arozumenko/sdlc-skillsWrote 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/arozumenko/sdlc-skills/journeys-to-hypotheses)<a href="https://agentmods.dev/skills/arozumenko/sdlc-skills/journeys-to-hypotheses"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/journeys-to-hypotheses/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/arozumenko/sdlc-skills/journeys-to-hypotheses"><img src="https://agentmods.dev/badge/skills/arozumenko/sdlc-skills/journeys-to-hypotheses.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 117 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00168 | $0.02187 |
| Opus 5 | $0.00084 | $0.01094 |
| Sonnet 5 | $0.00034 | $0.00437 |
| Haiku 4.5 | $0.00017 | $0.00219 |
Grade A, and why
journeys-to-hypotheses 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 12d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
journeys-to-hypotheses
The PO thinks in journeys and BDD — those are native artifacts, and good ones. The pipeline speaks problems → hypotheses → specs → epics. This skill is the translator between the two formats, and the guard against the most expensive failure mode in a multi-person backlog: re-deriving work that already exists on the board.
Audience calibration: the product owner is a senior product professional. The journeys are their product judgment — don't second-guess the content. What this skill adds is the mechanical translation into pipeline artifacts and the cross-check against whatever tracker board they have no reason to have memorized.
What this skill reads (config, by name)
From .agents/profile.md and the project's docs/ — read for:
- The issue tracker adapter (optional) — if
.agents/profile.mdnames one, use it for the cross-check in Step 1.3. If none is configured, skip the tracker entirely and say so; this is a degrade, not a failure. - The stakeholder/persona cast — journeys should reference the canonical persona slugs that
define-personasmaintains underdocs/discovery/personas/.
And these docs/discovery/ locations: journeys/ (source), hypotheses/ (source + mint target),
problems/ (mint target), and journey-coverage.md (the derived board this skill regenerates).
Step 1 — Inventory (read everything before classifying anything)
- Journeys: every journey map, the journey list, and the BDD scenarios (if present) in
docs/discovery/journeys/. Note per journey: persona, surface, and whether it has step-level detail or is only a map node. - Hypotheses: every file in
docs/discovery/hypotheses/— id, title, scope, persona. The lifecycle (status: incubating|promoted|parked) is a frontmatter field here, not a folder — read all of them regardless of status. - The tracker (optional — degrade gracefully): if
.agents/profile.mdnames an issue tracker, read its epic issues via the matching adapter:- GitHub →
gh issue list -R <repo> --limit 100 --state all --json number,title,body. - GitLab → the equivalent
glab issue listcall. - No tracker configured, or the adapter call fails → skip the tracker cross-check, mark
every board column n/a, and mark every verdict provisional (there is no committed
skeleton to cross-check against). Say so plainly in the report; do not fail the run.
Also read any committed epic specs the project's
docs/points at, if any.
- GitHub →
- Personas:
docs/discovery/personas/— journeys should reference canonical persona slugs (define-personasmaintains them).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 134 lines · 168 tokens per session scan A 1ee256829eaf
journeys-to-hypotheses is a skill published in the GitHub repository arozumenko/sdlc-skills (20 stars, last pushed yesterday), licensed MIT. It adds 168 tokens to every session and 2,187 once invoked, about $0.0008 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…