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-tech-designnpx skills add forthends/clockwork --skill create-tech-designgit 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.00798 |
| Opus 5 | $0.00000 | $0.00399 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
create-tech-design 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-tech-design - 一句话说明：基于 PRD 和模板，创建结构化的技术设计文档，涵盖架构、API 和数据模型
- 适用角色：Developer
触发条件
当以下条件满足时，应调用本技能：
- 工作流进入
tech_design阶段 - 需要将产品需求转化为技术实现方案
前置条件
调用本技能前，必须确保：
requirements阶段已完成（manifest.yaml 中 status 为completed）- PRD 文档
workflow/features/FEAT-<id>-<name>/prd.md已存在且通过校验 - 已读取工作流定义了解
tech_design阶段的输出要求
执行步骤
- 读取上游产物：读取
prd.md，逐条理解用户故事和验收标准 - 读取模板：读取
workflow/_templates/tech-design.md获取文档结构 - 设计架构（architecture 章节）：
- 确定整体技术方案和架构选型
- 绘制架构图，展示模块关系和数据流
- 划分模块职责，说明技术选型理由
- 记录关键设计决策及备选方案对比
- 设计 API（api_design 章节）：
- 为每个功能点定义 API 接口
- 包含：方法、路径、参数、请求体、响应体、错误码
- 确保接口设计覆盖 PRD 中所有用户故事
- 设计数据模型（data_model 章节）：
- 定义数据实体及字段
- 标注字段类型、约束和索引
- 绘制实体关系图
- 规划实现：
- 拆分实现任务并预估工时
- 识别技术风险和缓解措施
- 保存文件：将完成的技术设计保存到
workflow/features/FEAT-<id>-<name>/tech-design.md
输入
| 输入 | 来源 | 说明 |
|---|---|---|
| PRD 文档 | workflow/features/FEAT-<id>-<name>/prd.md |
产品需求和验收标准 |
| 技术设计模板 | workflow/_templates/tech-design.md |
文档结构模板 |
| 工作流定义 | workflow/_definitions/feature.yaml |
了解 validation 校验规则 |
输出
| 输出 | 路径 | 说明 |
|---|---|---|
| 技术设计文档 | workflow/features/FEAT-<id>-<name>/tech-design.md |
完整的技术设计方案 |
质量检查
完成技术设计后，对照以下清单自检：
- architecture 章节是否包含方案说明和架构图
- 每个设计决策是否说明了选择理由
- api_design 是否覆盖了 PRD 中的所有功能点
- 每个 API 接口是否包含完整的请求/响应定义
- data_model 是否包含所有实体和字段说明
- 实体间关系是否清晰
- 技术风险是否已识别
- 对 PRD 中有疑问的部分是否标注了
[待确认]
完成自检后，调用 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 cfdcf2d03a0e
create-tech-design 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 798 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…