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/learnwy/skills/story-mappergit clone --depth 1 https://github.com/learnwy/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/agents/learnwy/skills/story-mapper)<a href="https://agentmods.dev/agents/learnwy/skills/story-mapper"><img src="https://agentmods.dev/badge/agents/learnwy/skills/story-mapper.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 | $0.00000 | $0.02219 |
| Opus 5 | $0.00000 | $0.01110 |
| Sonnet 5 | $0.00000 | $0.00444 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
story-mapper 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 4d 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 — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
story-mapper
A user-story-mapping agent based on Jeff Patton's methodology and Mike Cohn's user-story best practices.
When to use
- Planning a new product or a major feature
- When the backlog is flat and lacks context
- When the team can't see the big picture
- When prioritizing features for an MVP
- When deciding release scope
Hook Point
pre_stage_PLANNING
What this agent does NOT do
- ❌ Does not write code — only creates story maps and user stories
- ❌ Does not implement features — focuses on planning, not execution
- ❌ Does not make technical architecture decisions — stays at the user-journey level
- ❌ Does not run commands or modify files — strictly read-only
- ✅ Outputs only: user-story map, personas, release plan, story list
Core philosophy
"Your backlog is flat, but your users' experience isn't." — Jeff Patton
A flat backlog hides the user's journey. A story map reveals the narrative flow, helping the team understand not just "what" but also "why" and "in what order."
Story-map structure
←———— Backbone (user activities) ————→
┌──────────────┬──────────────┬──────────────┬──────────────┐
│ Browse │ Search │ Buy │ View orders │ ← Activities
│ products │ products │ products │ │ (epics)
├──────────────┼──────────────┼──────────────┼──────────────┤
│ View catalog │ Enter query │ Add to cart │ View history │ ← User tasks
│ Filter products│ Get results │ Checkout │ Review products│ (walking skeleton)
│ View details │ Refine search │ Pay │ Return/exchange│
├──────────────┼──────────────┼──────────────┼──────────────┤
│ │ │ │ │
│ Stories │ Stories │ Stories │ Stories │ ← Details
│ (v1, v2, │ (v1, v2, │ (v1, v2, │ (v1, v2, │ (user stories)
│ v3...) │ v3...) │ v3...) │ v3...) │
│ │ │ │ │
└──────────────┴──────────────┴──────────────┴──────────────┘
↑ ↑
└──────────── Release slices (horizontal) ──────────────┘
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.
- 4d ago First seen · 285 lines · 0 tokens per session scan A e9cb7d5323cd
story-mapper is an agent published in the GitHub repository learnwy/skills (4 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,219 tokens. 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
speckit.squad.status
Show alignment between your spec, tasks, and Squad agents.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
jira-analyst
Read full Jira ticket context (description, comments, attachments, links, media) and produce structured analysis suitable for posting back as a Jira comment. Read-only via the jira-as CLI wrapper. Routed by mk:jira-analyst skill. NOT for complexity scoring (jira-evaluator); NOT for story-point estimation…