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/validate-artifactnpx skills add forthends/clockwork --skill validate-artifactgit 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.02831 |
| Opus 5 | $0.00000 | $0.01416 |
| Sonnet 5 | $0.00000 | $0.00566 |
| Haiku 4.5 | $0.00000 | $0.00283 |
Grade A, and why
validate-artifact 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.
How it starts
The opening of the file, as written. The whole thing — 293 lines — stays where its author put it; the contents beside it link to each section on GitHub.
校验产物质量
技能信息
- 技能名称：校验产物质量
- 技能标识：
validate-artifact - 一句话说明：对产物进行结构完整性和内容质量双重校验，确保符合质量闸门标准
- 适用角色：PM / Developer / Tester / Reviewer（所有角色通用）
触发条件
当以下条件满足时，应调用本技能：
- 某个阶段的产物编写完成，需要进行质量校验
- 产物修改后需要重新校验
- 流程推进前的最后检查
前置条件
调用本技能前，必须确保：
- 产物文件已创建并保存到
workflow/features/FEAT-<id>-<name>/目录 - 工作流定义文件存在于
workflow/_definitions/目录 - manifest.yaml 中该阶段
status为in_progress
校验类型
本技能执行三类校验，层层递进：
| 校验类型 | 说明 | 失败后果 |
|---|---|---|
| S1 - 结构校验 | 产物是否包含所有必需章节 | 阻塞 → 必须修复 |
| S2 - 内容校验 | 章节内容是否有实质意义（非空占位符） | 阻塞 → 必须修复 |
| S3 - 引用校验 | 跨文件引用是否准确存在 | 阻塞 → 必须修复 |
执行步骤
第一步：读取上下文
- 读取
workflow/features/FEAT-<id>-<name>/manifest.yaml - 从 manifest 获取
workflow名称和当前阶段id - 读取
workflow/_definitions/<workflow>.yaml - 定位当前阶段的
outputs[].validation规则
第二步：S1 - 结构校验
读取产物文件，按 required_sections 逐项检查：
检查清单：
[ ] 章节是否存在（按 `##` 或 `###` 标题识别）
[ ] 章节是否为空（仅有标题无正文内容）
失败条件：任何 required_section 缺失或为空
第三步：S2 - 内容校验
对每个已通过的章节，进行深度内容检查：
通用规则（所有产物适用）
| 规则 | 检查逻辑 | 失败原因示例 |
|---|---|---|
no_placeholder |
内容不能仅含 <占位符> 模式 |
发现 "<描述需求产生的背景>" 等未填充占位符 |
no_lorem |
不能包含 lorem ipsum 等占位文本 | 发现 "Lorem ipsum dolor sit amet" |
meaningful_length |
正文内容至少 50 字符 | 章节存在但内容仅 20 字符 |
领域规则（按产物类型启用）
PRD (prd.md) 专用规则：
| 规则 | 检查逻辑 | 失败原因示例 |
|---|---|---|
ac_actionable |
acceptance_criteria 每条必须包含"操作"和"预期结果" | AC 条目缺少"操作"或"预期结果"字段 |
ac_verifiable |
验收标准必须可验证（不能是主观描述） | "界面美观" 等无法客观验证的描述 |
story_complete |
每个 user_story 必须包含"作为/我想要/以便"三要素 | 故事缺少"以便"字段 |
scope_boundary |
必须明确区分"包含"和"不包含" | 范围界定模糊或缺失"不包含"部分 |
技术设计 (tech-design.md) 专用规则：
| 规则 | 检查逻辑 | 失败原因示例 |
|---|---|---|
has_api_contract |
api_design 章节必须定义端点、请求、响应 | API 设计缺少请求/响应格式定义 |
has_data_model |
data_model 章节必须包含实体关系或表结构 | 数据模型缺失或过于简略 |
no_impl_details |
architecture 章节不能包含具体代码实现 | 发现具体的函数实现代码 |
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 · 293 lines · 0 tokens per session scan A 8a2a12cebe75
validate-artifact 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 2,831 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.