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.
git 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/commands/killvxk/pm-skills-zh/test-scenarios)<a href="https://agentmods.dev/commands/killvxk/pm-skills-zh/test-scenarios"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/test-scenarios/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/commands/killvxk/pm-skills-zh/test-scenarios"><img src="https://agentmods.dev/badge/commands/killvxk/pm-skills-zh/test-scenarios.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.00023 | $0.00758 |
| Opus 5 | $0.00012 | $0.00379 |
| Sonnet 5 | $0.00005 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
test-scenarios 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
/test-scenarios -- 测试场景生成器
将用户故事或功能描述转化为 QA 可立即执行的综合测试场景，涵盖正常流程、边界情况、错误处理及跨浏览器/设备兼容性注意事项。
Invocation（调用示例）
/test-scenarios [粘贴用户故事或验收标准]
/test-scenarios [上传 PRD 或功能规格]
/test-scenarios 用户可以通过邮件链接重置密码
Workflow（工作流程）
Step 1：接收输入
接受：用户故事、验收标准、PRD（产品需求文档）章节、功能描述，或任何对预期行为的规格说明。
Step 2：生成测试场景
应用 test-scenarios 技能：
针对每个用户故事或需求，生成：
正常流程场景：预期用户流程正常运行 边界情况：边界条件、异常输入、并发操作 错误场景：出错时系统的表现 安全场景：如适用（认证、权限、数据访问） 性能场景：如适用（负载、超时、大数据量）
Step 3：结构化输出
## 测试场景：[功能名称]
**来源**: [用户故事 / PRD / 描述]
**场景总数**: [数量]
**覆盖范围**: [正常流程 / 边界情况 / 错误处理 / 安全 / 性能]
### 场景 1：[标题]
**测试对象**: [对应哪个故事或需求]
**前置条件**: [所需准备工作]
**用户角色**: [执行此操作的人]
| 步骤 | 操作 | 预期结果 |
|------|------|---------|
| 1 | [用户操作] | [系统预期响应] |
| 2 | [用户操作] | [系统预期响应] |
**后置条件**: [完成后的系统状态]
**优先级**: [关键 / 高 / 中 / 低]
---
[对每个场景重复以上格式]
### 覆盖矩阵
| 需求 | 正常流程 | 边界情况 | 错误处理 | 备注 |
|------|---------|---------|---------|------|
### 测试数据需求
[执行这些场景所需的测试数据]
保存为 Markdown 格式。
Step 4：提供后续建议
- "需要我为这些场景生成测试数据吗？"
- "需要我为某个特定场景补充更多边界情况吗？"
- "需要我创建这些场景所测试的用户故事吗？"
Notes（注意事项）
- 先写正常流程，再逐步覆盖边界情况——确保基础流程正常后再测试边界
- 原始故事中的每一条验收标准都应对应至少一个测试场景
- 同时包含正向测试（功能正常运行）和负向测试（优雅地处理失败）
- 对于 API，包含限流、超时、格式错误的请求和认证失败的场景
- 标注需要特定测试环境或第三方服务模拟的场景
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 · 84 lines · 23 tokens per session scan A c6732c2d25b0
test-scenarios is a command published in the GitHub repository killvxk/pm-skills-zh (158 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 758 once invoked, about $0.0001 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.