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 forthends/clockwork --skill create-prdgit clone --depth 1 https://github.com/forthends/clockworkWrote 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/forthends/clockwork/create-prd)<a href="https://agentmods.dev/skills/forthends/clockwork/create-prd"><img src="https://agentmods.dev/badge/skills/forthends/clockwork/create-prd/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/forthends/clockwork/create-prd"><img src="https://agentmods.dev/badge/skills/forthends/clockwork/create-prd.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.00000 | $0.00759 |
| Opus 5.5 | $0.00000 | $0.00304 |
| Sonnet 5.5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
create-prd 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 2mo 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
创建产品需求文档（PRD）
技能信息
- 技能名称：创建 PRD
- 技能标识：
create-prd - 一句话说明：基于模板和用户需求描述，创建结构化的产品需求文档
- 适用角色：PM
触发条件
当以下条件满足时，应调用本技能：
- 用户要求创建新的产品需求
- 工作流进入
requirements阶段 - 需要将口头需求转化为正式的 PRD 文档
前置条件
调用本技能前，必须确保：
- 已创建需求实例目录
workflow/features/FEAT-<id>-<name>/ - 已初始化
manifest.yaml，requirements阶段状态为in_progress - 已读取工作流定义
workflow/_definitions/feature.yaml了解输出要求
执行步骤
- 读取模板：读取
workflow/_templates/prd.md获取文档结构 - 收集信息：与用户充分沟通，了解需求背景、目标用户和期望功能
- 填写概述（overview 章节）：
- 描述需求背景和业务场景
- 明确核心目标，尽量量化
- 界定需求范围（包含/不包含）
- 编写用户故事（user_stories 章节）：
- 遵循 "作为[角色]，我想要[功能]，以便[价值]" 格式
- 每个独立的用户行为路径对应一个故事
- 补充必要的上下文和约束说明
- 定义验收标准（acceptance_criteria 章节）：
- 每个用户故事至少一条验收标准
- 包含前置条件、操作步骤和预期结果
- 确保可量化、可验证
- 补充信息：
- 非功能性需求（性能、安全、兼容性）
- 依赖与风险分析
- 优先级评估
- 保存文件：将完成的 PRD 保存到
workflow/features/FEAT-<id>-<name>/prd.md
输入
| 输入 | 来源 | 说明 |
|---|---|---|
| 需求描述 | 用户口述 | 用户对需求的自然语言描述 |
| PRD 模板 | workflow/_templates/prd.md |
文档结构模板 |
| 工作流定义 | workflow/_definitions/feature.yaml |
了解 validation 校验规则 |
输出
| 输出 | 路径 | 说明 |
|---|---|---|
| PRD 文档 | workflow/features/FEAT-<id>-<name>/prd.md |
完整的产品需求文档 |
质量检查
完成 PRD 后，对照以下清单自检：
- overview 章节是否完整（背景、目标、范围）
- 用户故事是否覆盖所有功能点
- 用户故事格式是否规范（角色、功能、价值）
- 每个用户故事是否有对应的验收标准
- 验收标准是否可量化、可验证
- 非功能性需求是否有考虑
- 依赖和风险是否有识别
完成自检后，调用 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.
- 2mo ago First seen · 89 lines · 0 tokens per session scan A e23c417657d5
create-prd is a skill published in the GitHub repository forthends/clockwork (8 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 759 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…