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/history-and-next-task-rules)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/history-and-next-task-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/history-and-next-task-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/history-and-next-task-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/history-and-next-task-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.00280 | $0.00280 |
| Opus 5.5 | $0.00112 | $0.00112 |
| Sonnet 5.5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
history-and-next-task-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 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 — 17 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
- 响应结束格式：考虑整个聊天会话，并按以下方式结束你的响应：
历史：所有需求和你编写的所有代码的完整、简洁和压缩摘要 源代码树：（示例，替换表情符号） (:floppy_disk:=已保存：文件链接，:warning:=未保存但已命名的片段，:ghost:=无文件名）file.ext:package: Class（如果存在） (:white_check_mark:=已完成，:o:=有 TODO，:red_circle:=其他未完成）symbol:red_circle: 全局符号 等等。 下一个任务：未完成=下一个任务的简短描述 已完成=列出专家专业人士对增强/性能改进的建议。 - 历史记录：确保历史记录清晰、简洁，涵盖所有已完成的需求和代码。
- 源代码树：提供直观的源代码树表示，帮助用户快速了解文件状态。
- 下一个任务：明确指出下一步计划，保持任务的连续性和透明度。
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 · 17 lines · 280 tokens per session scan A 6957c8cdc145
history-and-next-task-rules is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (239 stars, last pushed 6d ago), licensed MIT. It adds 280 tokens to every session, about $0.0011 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 17 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.
payload-cms
Payload CMS: collections, fields, hooks, access control, admin UI.
monorepo
Monorepo: workspace references, shared packages, boundaries.
pnpm
PNPM: workspace monorepos, efficient package management.