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 Omar-Obando/qwen-orchestrator --skill user-story-mappinggit clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/user-story-mapping)<a href="https://agentmods.dev/skills/omar-obando/qwen-orchestrator/user-story-mapping"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/user-story-mapping/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/omar-obando/qwen-orchestrator/user-story-mapping"><img src="https://agentmods.dev/badge/skills/omar-obando/qwen-orchestrator/user-story-mapping.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.00055 | $0.02643 |
| Opus 5 | $0.00028 | $0.01321 |
| Sonnet 5 | $0.00011 | $0.00529 |
| Haiku 4.5 | $0.00006 | $0.00264 |
Grade A, and why
user-story-mapping 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 9d 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 — 305 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Story Mapping Skill — Product Owner
Overview
This skill provides comprehensive guidance for user story mapping, including creating story maps, breaking down epics, organizing features by timeline, and visualizing product backlog. It covers story mapping workshops, epic decomposition, and feature prioritization following Jeff Patton's methodology.
When to Use
Use this skill when:
- Creating user story maps for products
- Breaking down epics into user stories
- Organizing features by user workflow
- Creating product backlogs
- Facilitating story mapping workshops
- Prioritizing features for release planning
- Visualizing product roadmap
- Aligning stakeholders on features
- Decomposing complex features
- Creating user journey maps
- Mapping user flows
- Identifying minimum viable products
- Planning releases based on stories
- Creating sprint backlogs from story maps
- Aligning development team on features
- Creating acceptance criteria from stories
- Mapping user roles and personas
- Creating feature dependencies
- Identifying gaps in features
- Planning MVP scope
- Creating product vision
- Aligning on product goals
Do NOT use this skill when:
- Writing application business logic (use domain-driven skill)
- Designing database schemas (use database-design skill)
- Writing API endpoint specifications (use api-design skill)
- Performing security audits (use security-auditor skill)
- Writing SQL queries (use sql-best-practices skill)
- Designing multi-page website layouts (use design-system skill)
- Analyzing deployment configurations (use deployment skill)
- Writing documentation (use documentation-best-practices skill)
User Story Map Structure
Basic Story Map
┌─────────────────────────────────────────────────────────────┐
│ User Story Map │
├─────────────────────────────────────────────────────────────┤
│ User Goal / Activity │
│ └── Task 1 │
│ ├── Story 1.1 │
│ ├── Story 1.2 │
│ └── Story 1.3 │
│ └── Task 2 │
│ ├── Story 2.1 │
│ ├── Story 2.2 │
│ └── Story 2.3 │
│ └── Task 3 │
│ ├── Story 3.1 │
│ ├── Story 3.2 │
│ └── Story 3.3 │
│ │
│ Release 1: Story 1.1, Story 1.2, Story 2.1 │
│ Release 2: Story 1.3, Story 2.2, Story 3.1 │
│ Release 3: Story 2.3, Story 3.2, Story 3.3 │
└─────────────────────────────────────────────────────────────┘
What ships with it
1 file 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.
- 9d ago First seen · 305 lines · 55 tokens per session scan A da1e66d183a9
user-story-mapping is a skill published in the GitHub repository Omar-Obando/qwen-orchestrator (49 stars, last pushed 2mo ago), licensed MIT. It adds 55 tokens to every session and 2,643 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
loopx-project
Use when connecting a repository or project goal document to LoopX, maintaining project-local goal state, refreshing stale dashboard status, syncing local projects into the shared global registry, or diagnosing LoopX CLI/PATH/status/history issues across multiple repos. For registering durable project materials such…
pm
Generate a PM through guided PM-focused interview with automatic question classification. Use when the user says 'ooo pm', 'prd', 'product requirements', or wants to create a PRD/PM document.
publish
Publish Seed specification as GitHub Issues for team-based project management.
loopx-material
Operate an explicitly activated LoopX Material Lifecycle for a connected project. Use for material-store inventory, lossless migration, candidate/archive transitions, exact-read-backed ranking, ranked-entry rebuilds, bounded Explore intake, owner-gated apply, rollback, and audit. Do not use for ordinary one-off…
loopx-pr-program
Use when LoopX must manage a multi-PR or multi-MR delivery program across one or more repositories: inventory current change requests, reconcile new/merged/closed or retargeted work, preserve requirement and dependency priorities, maintain a roadmap document, or monitor material lifecycle/check/review changes over…
loopx-manager
Inspect authorized LoopX Goals, Todos and deliveries to explain progress, identify owner decisions and delegate intent to the right worker.