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 job-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/job-stories)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/job-stories"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/job-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/job-stories"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/job-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.00071 | $0.00824 |
| Opus 5 | $0.00036 | $0.00412 |
| Sonnet 5 | $0.00014 | $0.00165 |
| Haiku 4.5 | $0.00007 | $0.00082 |
Grade A, and why
job-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 11d 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
工作故事（Job Stories）
使用「当 [情境] 时，我想要 [动机]，以便 [结果]」格式创建工作故事，聚焦于用户情境和成果，附带详细的验收标准。
适用场景： 编写工作故事、表达用户情境和动机、创建 JTBD（Jobs-to-be-Done，用户待办任务）风格的待办事项，或聚焦用户背景而非角色时。
参数：
$PRODUCT：产品或系统名称$FEATURE：需要拆解为工作故事的新功能$DESIGN：设计文件链接（Figma、Miro 等）$CONTEXT：用户情境或工作场景
Step-by-Step Process（分步流程）
- 识别触发需求的用户情境
- 定义用户行为背后的动机
- 明确用户想要实现的结果
- 应用 JTBD 框架： 聚焦于工作本身，而非角色
- 创建验收标准， 验证成果是否已实现
- 使用可观察、可量化的语言
- 链接设计原型或 Mockup
- 输出带详细验收标准的工作故事
Story Template（故事模板）
标题： [工作成果或结果]
描述： 当 [情境] 时，我想要 [动机]，以便 [结果]。
设计： [设计文件链接]
验收标准：
- [情境被正确识别]
- [系统支持预期的动机]
- [进度或反馈可见]
- [成果被高效实现]
- [边界情况被优雅处理]
- [集成和通知正常运行]
Example Job Story（工作故事示例）
标题： 追踪每周零食花费
描述： 当我在规划每周零食预算时（情境），我想要快速了解到目前为止花了多少钱（动机），以便确保在周末前不会花光零花钱（结果）。
设计： [Figma 链接]
验收标准：
- 显示"每周消费概览"板块，包含消费汇总
- 记录支出时实时更新
- 进度指示器（显示每周预算使用 0-100% 的进度条）
- 以醒目颜色突出显示剩余预算金额
- 详细消费记录，按类别分类展示
- 在预算使用达到 80% 时发送通知
- 在周四晚上预算使用达到 90% 时发送周末专属提醒
- 便于访问并可跳转至详细消费明细
Output Deliverables（输出交付物）
- 该功能的完整工作故事集
- 每个故事遵循「当……我想要……以便……」格式
- 6-8 条聚焦于成果的验收标准
- 故事强调用户情境和动机
- 包含清晰的设计和原型链接
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.
- 11d ago First seen · 75 lines · 71 tokens per session scan A 993ffe99f568
job-stories is a skill published in the GitHub repository killvxk/pm-skills-zh (159 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 824 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…