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-guidelines)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/build-notes-guidelines"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/build-notes-guidelines/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-guidelines"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/build-notes-guidelines.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.00183 | $0.00183 |
| Opus 5.5 | $0.00073 | $0.00073 |
| Sonnet 5.5 | $0.00037 | $0.00037 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
build-notes-guidelines 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 1mo 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.
This is a copy
100% identical to strategic-planning-with-pseudocode — 8 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- 你必须为每个任务组创建一个"构建笔记"文件来跟踪我们工作的任务组的进度。
- 清晰和简洁： 保持笔记简洁、直接，专注于手头的任务。
- 逻辑命名： 使用一致的命名约定，将每个笔记文件与特定任务和日期联系起来。
- 增量更新： 随着计划演进或任务完成更新笔记。追加而不是覆盖。
- 可追溯性： 确保每个决策或方法变更都被记录且易于跟踪。
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.
- 1mo ago First seen · 10 lines · 183 tokens per session scan A a48eab6539a1
build-notes-guidelines is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (239 stars, last pushed 5d ago), licensed MIT. It adds 183 tokens to every session, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to strategic-planning-with-pseudocode, differing in 8 lines, and is treated as a copy.
Other cursor rules, from other repositories
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
qa-bug-report-cursorrules-prompt-file
Cursor rules for QA development with bug report integration.
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
payload-cms
Payload CMS: collections, fields, hooks, access control, admin UI.
monorepo
Monorepo: workspace references, shared packages, boundaries.