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 konglong87/superPM --skill pm-user-storygit clone --depth 1 https://github.com/konglong87/superPMWrote 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/konglong87/superpm/pm-user-story)<a href="https://agentmods.dev/skills/konglong87/superpm/pm-user-story"><img src="https://agentmods.dev/badge/skills/konglong87/superpm/pm-user-story/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/konglong87/superpm/pm-user-story"><img src="https://agentmods.dev/badge/skills/konglong87/superpm/pm-user-story.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.00054 | $0.02814 |
| Opus 5.5 | $0.00022 | $0.01126 |
| Sonnet 5.5 | $0.00011 | $0.00563 |
| Haiku 4.5 | $0.00005 | $0.00281 |
Grade A, and why
pm-user-story 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 — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Preamble (run first)
# 检查方案设计目录
# 检查前置文档
echo "📊 正在检查前置文档..."
if [ -f "docs/02-方案设计/PRD产品需求文档.md" ]; then
echo "✅ PRD文档 - 已找到"
else
echo "⏳ PRD文档 - 未找到"
fi
if [ -f "docs/02-方案设计/功能细节拆解.md" ]; then
echo "✅ 功能细节拆解 - 已找到"
else
echo "⏳ 功能细节拆解 - 未找到"
fi
写入时边界
只讨论时不写文件，启动检查不创建目录。用户要求保存产物时，先确认当前产品、精确输出路径及已有文件的覆盖/追加选择；确认后仅在实际 Write 前创建该输出文件的父目录。完整安装可参见 skills/_shared/artifact-policy.md，单独安装本 skill 也按本段执行。
跨 Agent 交互规则
当流程要求与用户交互时：
- 如果当前环境支持 AskUserQuestion，使用 AskUserQuestion（最佳体验）。
- 如果当前环境不支持 AskUserQuestion，必须用普通聊天消息提出同样问题。
- 一次只问一个问题。
- 提问后必须停止当前回合，等待用户回答（STOP and WAIT）。
- 不得在用户回答前生成文档、写入 docs。
- 已有 docs 文件不能替代本轮用户回答。
执行流程
步骤 1: 选择用户故事范围
使用 AskUserQuestion 询问：
您需要编写哪方面的用户故事？
A) 全部功能用户故事（基于PRD功能列表） B) 单个模块的用户故事（请指定模块） C) 单个功能的用户故事（请指定功能） D) Epic级用户故事（高层次需求） E) 其他（请手动输入）
💡 提示：
- Sprint规划 → 推荐单个模块的用户故事
- 产品规划 → 推荐Epic级用户故事
- 开发准备 → 推荐全部功能用户故事
记录到变量 STORY_SCOPE
步骤 2: 读取前置数据
根据范围读取相应文档：
必需文档：
- PRD产品需求文档（如果存在）
- 功能细节拆解（如果存在）
可选文档：
- MVP方案
- 用户画像
读取失败处理：
如果 PRD 文档不存在：
⚠️ 未找到 PRD 文档
用户故事需要明确的功能需求作为输入。
您可以选择： A) 执行 /pm-docs 生成 PRD B) 使用功能细节拆解作为输入 C) 手动输入功能需求（快速模式）
步骤 3: 用户故事编写原则
📝 用户故事标准格式：
作为 <角色> 我想要 <功能> 以便于 <价值>验收标准（BDD格式）：
GIVEN <前置条件> WHEN <触发操作> THEN <预期结果>是否继续编写？
A) 理解了，开始编写 B) 我需要更多示例 C) 我有特定的编写规范
步骤 4: Epic级用户故事
4.1 识别Epic
基于PRD识别出Epic：
| Epic ID | Epic名称 | 描述 | 包含Story数 |
|---|---|---|---|
| E001 | 用户管理 | 用户注册、登录、信息管理 | 5 |
| E002 | 商品浏览 | 商品列表、搜索、详情 | 4 |
| E003 | 购物车管理 | 加入购物车、编辑、结算 | 3 |
| E004 | 订单管理 | 订单创建、支付、查看 | 6 |
是否需要调整Epic划分？
A) 划分合理，继续 B) 需要调整 C) 我有其他划分方式
4.2 Epic详细描述
对每个Epic进行描述：
**Epic: E001 用户管理**
作为 产品系统
我想要 提供用户管理功能
以便于 用户可以注册登录，管理个人信息
业务价值：
- 用户可以拥有个人账号
- 支持个性化服务
- 提供用户数据用于数据分析
包含Story：US001-US005
优先级：P0
预估工时：5人天
逐个对每个Epic确认后继续。
步骤 5: Story级用户故事
5.1 逐个编写Story
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 Changed · +4 lines ddf4e70ab510
- 1mo ago First seen · 368 lines · 54 tokens per session scan A 5c8f6aeee5ad
pm-user-story is a skill published in the GitHub repository konglong87/superPM (84 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 2,814 once invoked, about $0.0002 per session on Opus 5.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
team-tasks
Coordinate multi-agent development pipelines using shared JSON task files. Use when dispatching work across dev team agents (code-agent, test-agent, docs-agent, monitor-bot), tracking pipeline progress, or running sequential/parallel workflows. Covers project init, task assignment, status tracking, agent dispatch via…
multi-search
A web-search helper that chooses among DuckDuckGo, Tavily, Bing API, and Bing scraping based on the available network.
add-linear
Add Linear channel integration via Chat SDK. Issue comment threads as conversations.
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
slack-construct-agents
Standing context for Slack sibling agents — one room per team, creator-posted introductions, bot-to-bot hop discipline. Ships as instructions.md composed into the group's CLAUDE.md at spawn; there is no workflow to invoke.
ledger-tasks-yylo
Comprehensive guide for using YYLO Ledger task management without bypassing controller routing, lifecycle state, or mutation receipts. Covers task commands, dependency management, best practices, and workflow patterns. Use when you need to interact with the YYLO Ledger board.