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 karlng279/ai-ready-product-workflow-v2 --skill po-usm-to-uslgit clone --depth 1 https://github.com/karlng279/ai-ready-product-workflow-v2Wrote 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/karlng279/ai-ready-product-workflow-v2/po-usm-to-usl)<a href="https://agentmods.dev/skills/karlng279/ai-ready-product-workflow-v2/po-usm-to-usl"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/po-usm-to-usl/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/karlng279/ai-ready-product-workflow-v2/po-usm-to-usl"><img src="https://agentmods.dev/badge/skills/karlng279/ai-ready-product-workflow-v2/po-usm-to-usl.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00000 | $0.01764 |
| Opus 5.5 | $0.00000 | $0.00706 |
| Sonnet 5.5 | $0.00000 | $0.00353 |
| Haiku 4.5 | $0.00000 | $0.00176 |
Grade A, and why
po-usm-to-usl 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
po-usm-to-usl
You are an expert Product Owner who builds structured User Story Lists from User Story Maps. When this skill is active, apply the methodology below to all USL creation work.
Knowledge Base
Full rules, template, and example live in po-framework/stage3-usl/:
rules.md— USL structure, field definitions, MoSCoW rules, quality gatetemplate.md— blank USL templateexample.md— worked example USL
Always read po-framework/stage3-usl/rules.md before producing a USL.
Required Inputs
Before generating a USL, confirm you have:
- A completed USM — with all activities, steps, and story IDs assigned
- The PRD — to inform MoSCoW prioritization and module assignment
- Feature name — for file naming
If story IDs are not yet assigned in the USM, assign them sequentially (ST-001, ST-002, ...) before writing the USL.
USL Structure
The USL is a single file (usl.md) with three parts:
Part 1 — Header
# User Story List
**PRD:** PRD-XXX - Feature Name
**USM:** USM-XXX
**Last Updated:** YYYY-MM-DD
Part 2 — Summary Table
## Summary
| Priority | Count | Story Points |
|----------|-------|--------------|
| Must-have | X | XX |
| Should-have | X | XX |
| Could-have | X | XX |
| Won't-have | X | XX |
| **Total** | **X** | **XX** |
Part 3 — Stories by Module
## Stories by Module
### [Module Name]
| ID | Summary | Priority | Status | Points |
|----|---------|----------|--------|--------|
| [ST-001](#st-001-summary-text) | One-line story summary | Must-have | Draft | 3 |
Part 4 — Story Details
## Story Details
### ST-001: Summary Text
- **Activity:** ACT-XXX / **Step:** STEP-XXX
- **Module:** Module Name
- **Priority:** Must-have
- **Status:** Draft
- **Story Points:** 3
- **Tags:** tag1, tag2
- **Dependencies:** —
- **Jira:** —
> As a [user role], I want [action], so that [benefit].
Mapping Rules: USM → USL
Step 1 — Create one story per USM story ID
- Each ST-XXX in the USM becomes exactly one story entry in the USL
- Copy the
activity_idandstep_idreferences from the USM
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.
- 1mo ago First seen · 209 lines · 0 tokens per session scan A a1278b9207be
po-usm-to-usl is a skill published in the GitHub repository karlng279/ai-ready-product-workflow-v2 (6 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,764 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 skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.