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 agentmods add skills/forthends/clockwork/create-test-plannpx skills add forthends/clockwork --skill create-test-plangit clone --depth 1 https://github.com/forthends/clockworkWhat 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 | $0.00000 | $0.00838 |
| Opus 5 | $0.00000 | $0.00419 |
| Sonnet 5 | $0.00000 | $0.00168 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
create-test-plan 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 2d 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
创建测试计划
技能信息
- 技能名称：创建测试计划
- 技能标识：
create-test-plan - 一句话说明：基于 PRD 验收标准和技术设计文档，创建全面的测试计划
- 适用角色：Tester
触发条件
当以下条件满足时，应调用本技能：
- 工作流进入
testing阶段 - 需要编写测试计划和测试用例
前置条件
调用本技能前，必须确保：
requirements阶段已完成，PRD 文档存在且通过校验tech_design阶段已完成，技术设计文档存在且通过校验- 已读取工作流定义了解
testing阶段的输出要求
执行步骤
- 读取上游产物：
- 读取
prd.md，提取所有验收标准（AC-x） - 读取
tech-design.md，了解 API 接口和数据模型
- 读取
- 读取模板：读取
workflow/_templates/test-plan.md获取文档结构 - 定义测试范围（test_scope 章节）：
- 明确测试目标
- 界定范围内/外的功能
- 确定测试策略（功能、接口、边界、异常）
- 编写测试用例（test_cases 章节）：
- 功能测试用例：每条验收标准至少一个对应用例
- 包含：关联的 AC 编号、前置条件、操作步骤、预期结果、测试数据
- 异常场景用例：覆盖错误输入、边界条件、权限不足等场景
- 用例编号规则：功能测试
TC-xxx，异常测试TC-Exxx
- 功能测试用例：每条验收标准至少一个对应用例
- 定义测试环境（test_environment 章节）：
- 列出环境配置要求
- 描述测试数据准备方案
- 初始化进度追踪表：所有用例初始状态设为"待执行"
- 保存文件：将完成的测试计划保存到
workflow/features/FEAT-<id>-<name>/test-plan.md
输入
| 输入 | 来源 | 说明 |
|---|---|---|
| PRD 文档 | workflow/features/FEAT-<id>-<name>/prd.md |
验收标准和功能描述 |
| 技术设计文档 | workflow/features/FEAT-<id>-<name>/tech-design.md |
API 和数据模型细节 |
| 测试计划模板 | workflow/_templates/test-plan.md |
文档结构模板 |
| 工作流定义 | workflow/_definitions/feature.yaml |
了解 validation 校验规则 |
输出
| 输出 | 路径 | 说明 |
|---|---|---|
| 测试计划 | workflow/features/FEAT-<id>-<name>/test-plan.md |
完整的测试计划文档 |
质量检查
完成测试计划后，对照以下清单自检：
- test_scope 是否清晰定义了测试目标和范围
- 每条验收标准是否至少有一个对应的测试用例
- 测试用例格式是否完整（前置条件、步骤、预期结果）
- 是否覆盖了正常流程和异常流程
- 异常场景是否包含边界条件和错误输入
- 测试环境要求是否明确
- 测试数据准备方案是否可行
- 用例之间是否有遗漏的场景
完成自检后，调用 validate-artifact 技能进行正式校验。
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.
- 2d ago First seen · 89 lines · 0 tokens per session scan A fd0617ca9aca
create-test-plan is a skill published in the GitHub repository forthends/clockwork (8 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 838 tokens. 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…