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 killvxk/pm-skills-zh --skill user-storiesgit clone --depth 1 https://github.com/killvxk/pm-skills-zhWrote 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/killvxk/pm-skills-zh/user-stories)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/user-stories"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/user-stories/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/killvxk/pm-skills-zh/user-stories"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/user-stories.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.00066 | $0.00812 |
| Opus 5 | $0.00033 | $0.00406 |
| Sonnet 5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00007 | $0.00081 |
Grade A, and why
user-stories 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 10d 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.
What it actually says
用户故事（User Stories）
遵循 3C 原则（Card 卡片、Conversation 对话、Confirmation 确认）和 INVEST 标准创建用户故事，附带描述、设计链接和验收标准。
适用场景： 编写用户故事、将功能拆解为故事、创建待办事项，或定义验收标准。
参数：
$PRODUCT：产品或系统名称$FEATURE：需要拆解为故事的新功能$DESIGN：设计文件链接（Figma、Miro 等）$ASSUMPTIONS：关键假设或背景信息
Step-by-Step Process（分步流程）
- 分析功能，基于提供的设计和背景信息
- 识别用户角色及各自的用户旅程
- 应用 3C 原则框架：
- Card（卡片）：简短标题和一句话描述
- Conversation（对话）：详细的意图讨论
- Confirmation（确认）：清晰的验收标准
- 遵循 INVEST 标准： Independent（独立）、Negotiable（可协商）、Valuable（有价值）、Estimable（可估算）、Small（小）、Testable（可测试）
- 使用通俗语言，小学毕业生能理解
- 链接设计文件，提供视觉参考
- 以结构化格式输出用户故事
Story Template（故事模板）
标题： [功能名称]
描述： 作为 [用户角色]，我想要 [操作]，以便 [收益]。
设计： [设计文件链接]
验收标准：
- [清晰、可测试的标准]
- [可观察的行为]
- [系统正确验证]
- [边界情况处理]
- [性能或无障碍访问考量]
- [集成要点]
Example User Story（用户故事示例）
标题： 最近浏览区域
描述： 作为在线购物者，我想要在商品详情页看到「最近浏览」区域，以便轻松回顾我曾考虑过的商品。
设计： [Figma 链接]
验收标准：
- 对于在当前会话中至少浏览过 1 件商品的用户，「最近浏览」区域显示在商品详情页底部。
- 对于本次会话中访问第一件商品详情页的用户，该区域不显示。
- 当前商品本身被排除在展示列表之外。
- 该区域以商品卡片或缩略图的形式展示商品图片、标题和价格。
- 每张商品卡片标注浏览时间（如"5 分钟前浏览"）。
- 点击商品卡片可跳转至对应商品详情页。
Output Deliverables（输出交付物）
- 该功能的完整用户故事集
- 每个故事包含标题、描述、设计链接和 4-6 条验收标准
- 故事相互独立，可以任意顺序开发
- 故事规模适合一个 Sprint 周期完成
- 故事中包含相关设计文档的引用
Further Reading（延伸阅读）
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.
- 10d ago First seen · 75 lines · 66 tokens per session scan A 855e03f5f86d
user-stories is a skill published in the GitHub repository killvxk/pm-skills-zh (158 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 812 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-08-30.
Other skills, from other repositories
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.