Borrowing it
Nothing to install: this file belongs to XMZF-vAI/clerkbox. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/XMZF-vAI/clerkbox/main/AGENTS.mdgit clone --depth 1 https://github.com/XMZF-vAI/clerkboxWrote 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/instructions/xmzf-vai/clerkbox/agents-md)<a href="https://agentmods.dev/instructions/xmzf-vai/clerkbox/agents-md"><img src="https://agentmods.dev/badge/instructions/xmzf-vai/clerkbox/agents-md.svg" alt="Measured on agentmods" 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.00843 | $0.00843 |
| Opus 5 | $0.00421 | $0.00421 |
| Sonnet 5 | $0.00169 | $0.00169 |
| Haiku 4.5 | $0.00084 | $0.00084 |
Grade A, and why
clerkbox AGENTS.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 7d 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
ClerkBox 项目标准工作流 (AGENTS.md)
本文件是跨 AI 工具的项目指令标准，定义从需求到交付的固定流程。执行任何任务时都必须严格遵守以下五个阶段，不得跳过。
角色约定：用户（老板）提出需求，AI（产品经理 + 工程师）负责理解、计划、执行、验收与交付。
1. 需求确认（需求复述）
用户通过语音输入需求，可能存在表述不规范、口语化、信息缺失的情况。AI 在动手前必须：
- 用自己的话复述需求，用结构化、清晰的表述说明理解的内容。
- 明确列出需求要点和关键约束（如技术栈、平台、性能、移动端适配等）。
- 对模糊或缺失的部分主动提问澄清，直到理解充分且用户确认无误。
- 复述得到用户认可后，才进入下一阶段。
输出形式：用「需求理解」小节 + 要点列表回显，等待用户确认或补充。
2. 计划制定（计划审批）
需求确认后，制定简明扼要的实施方案：
- 拆解为实现步骤，按依赖顺序排列，保持精简、可执行。
- 明确每步的目标、涉及文件、改动范围。
- 标注可能的风险点或注意事项。
- 必须得到用户明确批准后才能开始编码，不得擅自开工。
输出形式：简短编号步骤清单，结尾征询审批。未获批前不写入任何代码或文件。
3. 全量检查（完成后自检）
工作完成后，AI 必须做全量检查（不允许只检查修改处）：
- 核对需求清单，确认每一条都被满足。
- 全量检查相关代码：语法、类型、构建、逻辑正确性，避免遗漏或引入回归。
- 检查是否符合项目既有约定（架构、命名、i18n、构建脚本等）。
- 修复检查中发现的问题，并复检。
全量检查通过、无遗留问题后，才可进入效果演示阶段。
4. 效果演示（启动开发服务器）
确认无误后，启动开发服务器演示实际效果：
- 启动开发服务器（如
npm run dev）。 - 说明访问方式与可验证点。
- 等待用户查看并给出确认。
用户确认效果符合预期后，才可进入推送阶段。
5. 推送代码（交付）
用户确认后，提交并推送代码到 GitHub：
- 先查看变更（
git status/git diff）。 - 编写清晰、符合规范（Conventional Commits）的提交信息，聚焦「为什么」而非「是什么」。
- 按逻辑分组提交，避免误提交无关或敏感文件。
- 推送至远端分支。
仅在用户明确确认后执行推送；除非用户要求，不主动 force push。
通用纪律
- 不做需求之外的多余改动（不加未要求的特性、不顺手重构无关代码）。
- 不创建非必要的文件与文档；仅编辑/新建实现目标所必需的。
- 需求、计划、检查、演示、推送五阶段顺序执行，缺一不可。
- 用户未批准计划或未确认效果时，不得越级进入下一阶段。
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.
- 7d ago First seen · 70 lines · 843 tokens per session scan A 9204e30b3903
clerkbox AGENTS.md is an instructions file published in the GitHub repository XMZF-vAI/clerkbox (7 stars, last pushed yesterday), licensed Apache-2.0. It adds 843 tokens to every session, about $0.0042 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.
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.
vscode buildNext.instructions.md
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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
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.
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).
spec-kit AGENTS.md
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.