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 wwasgit 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/wwas)<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/wwas"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/wwas/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/wwas"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/wwas.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.00070 | $0.00837 |
| Opus 5 | $0.00035 | $0.00418 |
| Sonnet 5 | $0.00014 | $0.00167 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
wwas 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
为什么-做什么-验收标准（WWA）
以「为什么-做什么-验收标准」（Why-What-Acceptance，简称 WWA）格式创建产品待办事项。生成独立、有价值、可测试的工作项，包含战略背景。
适用场景： 编写待办事项、创建产品增量、将功能拆解为工作项，或向团队传达战略意图时。
参数：
$PRODUCT：产品或系统名称$FEATURE：新功能或能力$DESIGN：设计文件链接（Figma、Miro 等）$ASSUMPTIONS：关键假设和战略背景
Step-by-Step Process（分步流程）
- 定义战略「为什么」 - 将工作与业务和团队目标挂钩
- 描述「做什么」 - 保持描述简洁，引用设计文件
- 编写验收标准 - 高层次的标准，而非详细规格
- 确保独立性 - 工作项可以任意顺序开发
- 保持可协商性 - 邀请团队讨论，而非施加约束
- 确保有价值 - 每个工作项交付可量化的用户或业务价值
- 确保可测试性 - 成果可被观察和验证
- 适当分配规模 - 小到足以在一个 Sprint 内估算完成
Item Template（工作项模板）
标题： [将交付的内容]
为什么： [1-2 句话，与战略背景和团队目标挂钩]
做什么： [简短描述和设计链接。最多 1-2 段。是讨论的备忘，而非详细规格。]
验收标准：
- [可观察结果 1]
- [可观察结果 2]
- [可观察结果 3]
- [可观察结果 4]
Example WWA Item（WWA 工作项示例）
标题： 实现实时消费追踪器
为什么： 用户需要对消费有即时反馈，才能做出有意识的预算决策。这直接支撑我们提升财务意识、减少超支的目标。
做什么： 添加一个实时消费追踪器，在用户记录支出时实时更新。追踪器显示用户当周消费金额与设定预算的对比情况。设计详见 [Figma 链接]。这是我们讨论的备忘——详细规格将在与团队的开发对话中逐步明确。
验收标准：
- 记录支出后 2 秒内消费总额更新
- 用进度条直观呈现预算使用进度
- 用户可以一目了然地看到剩余预算金额
- 系统正确处理多个支出类别
Output Deliverables（输出交付物）
- 该功能的完整待办事项集
- 每个工作项包含「为什么」、「做什么」和「验收标准」三个部分
- 工作项相互独立，可任意顺序交付
- 工作项规模适合在一个 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 · 70 lines · 70 tokens per session scan A 50693b451f2b
wwas is a skill published in the GitHub repository killvxk/pm-skills-zh (158 stars, last pushed 5mo ago), licensed MIT. It adds 70 tokens to every session and 837 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.
remove
Remove a deployed framework or addon from the current workspace.