clockwork copilot-instructions.md

Project instructions for Clockwork, an AI-agent governance framework that organizes feature work into defined stages and assigns each stage to a role. It describes the project layout, required documents, and command-line checks.

In plain words
What is it for?
Use it to create and advance feature workflows, produce the required planning and testing documents, validate completed work, and check workflow status.
Why use it?
It gives agents a consistent process for requirements, technical design, implementation, testing, and review, while keeping responsibilities separate.

Instructions file for GitHub Copilot

Install

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.

agentmods
npx agentmods add instructions/forthends/clockwork/copilot-instructions
Clone the repo
git clone --depth 1 https://github.com/forthends/clockwork

Made for: GitHub Copilot.

Per session 406 This file is loaded in full into every session.
When invoked 406 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00406 $0.00406
Opus 5 $0.00203 $0.00203
Sonnet 5 $0.00081 $0.00081
Haiku 4.5 $0.00041 $0.00041

Measured 2d ago against content hash b9c21c30d373, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

clockwork copilot-instructions.md 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.

.github/copilot-instructions.md · 49 lines

What it actually says

Clockwork 治理规则

你在一个使用 Clockwork AI Agent 治理框架的项目中工作。

项目结构

  • workflow/features/FEAT-xxx/ — 需求实例目录
  • workflow/features/FEAT-xxx/manifest.yaml — 工作流状态记录
  • workflow/_templates/ — 产物模板目录
  • skills/ — 可用技能目录

角色与职责

  • PM: 产品经理,负责需求定义,产出 prd.md
  • Developer: 开发者,负责技术设计(tech-design.md)和代码实现
  • Tester: 测试工程师,负责测试计划(test-plan.md)
  • Reviewer: 代码评审员,负责评审报告

工作流阶段顺序

feature-development 工作流:

  1. requirements — 需求定义 (PM)
  2. tech_design — 技术设计 (Developer)
  3. implementation — 代码实现 (Developer)
  4. testing — 测试计划 (Tester)
  5. review — 代码评审 (Reviewer)

产物模板

  • PRD: workflow/_templates/prd.md
  • 技术设计: workflow/_templates/tech-design.md
  • 测试计划: workflow/_templates/test-plan.md

工作规范

  • 基于模板创建产物,保持章节结构完整
  • 章节内容不得为空占位符 <...>
  • 不跳过任何工作流阶段
  • 不修改其他角色负责的产物

CLI 工具

python3 cli/clockwork.py create "功能名" --repo <repo>
python3 cli/clockwork.py advance <feature-id> <stage>
python3 cli/clockwork.py validate <feature-id>
python3 cli/clockwork.py status <feature-id>
Changes

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.

  1. 2d ago First seen · 49 lines · 406 tokens per session scan A b9c21c30d373

Subscribe to this mod's changes

clockwork copilot-instructions.md is an instructions file published in the GitHub repository forthends/clockwork (8 stars, last pushed 2mo ago), licensed MIT. It adds 406 tokens to every session, about $0.0020 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-31.

Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens