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.
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zhWrote 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/rules/holtwood/awesome-cursorrules-zh/build-notes-file-rules)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/build-notes-file-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/build-notes-file-rules/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/rules/holtwood/awesome-cursorrules-zh/build-notes-file-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/build-notes-file-rules.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.00570 |
| Opus 5 | $0.00000 | $0.00285 |
| Sonnet 5 | $0.00000 | $0.00114 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
build-notes-file-rules 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 6d 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
- 位置和命名：
- 将所有笔记文件存储在
/ProjectDocs/Build_Notes/中。 - 使用逻辑性、描述性的命名约定，例如
build-title_phase-#_task-group-name.md。 - 使用
<build-title>描述构建任务。 - 使用
<phase-#>为构建任务应用阶段编号。 - 使用
<task-group-name>描述任务组名称。 - 示例：
supabase-schema-standardization_phase-1_preparation-and-code-analysis.mdsupabase-schema-standardization是构建标题phase-1是阶段编号preparation-and-code-analysis是任务组名称
- 将所有笔记文件存储在
- 内容结构：
- 以简要的 任务目标 开始，总结你要实现的目标。
- 提供 当前状态评估：简短描述与构建任务相关的项目当前状态。
- 提供 未来状态目标：简短描述与构建任务相关的项目未来状态。
- 接着是 实施计划：包含检查清单 任务 的编号 步骤 列表，以实现未来状态。
- 随着任务完成更新 实施计划 并划掉不适用的任务。永远不要从计划中删除任务。
- 如果计划改变或演进，添加新的 步骤 或 任务，而不是覆盖之前的内容。
- 何时更新：
- 任务开始时： 创建或打开特定任务的笔记文件，在编码前记录初始计划。
- 任务执行期间： 当计划改变、出现困难或产生新见解时添加更新。
- 任务完成时： 附加所做工作的摘要并验证是否与原始目标一致。
- 风格和语调：
- 保持笔记简洁、切题，不包含无关评论。
- 维护逻辑顺序，使未来读者能够理解决策过程而不会混淆。
- 构建笔记的完成：
- 构建笔记完成后，将文件移动到
/ProjectDocs/Build_Notes/completed/目录。 - 如果构建笔记已弃用且不再需要，将文件移动到
/ProjectDocs/Build_Notes/archived/目录。
- 构建笔记完成后，将文件移动到
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.
- 6d ago First seen · 32 lines · 570 tokens per session scan A af049c178c9c
build-notes-file-rules is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (233 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 570 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-09-03.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.