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/no-unnecessary-updates-rule)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/no-unnecessary-updates-rule"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/no-unnecessary-updates-rule/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/no-unnecessary-updates-rule"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/no-unnecessary-updates-rule.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.00021 | $0.00035 |
| Opus 5 | $0.00010 | $0.00017 |
| Sonnet 5 | $0.00004 | $0.00007 |
| Haiku 4.5 | $0.00002 | $0.00003 |
Grade A, and why
no-unnecessary-updates-rule 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 9d 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 code-commenting-standards — 4 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.
The source is not reproduced here
Licensed MIT
The repository is licensed MIT, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 9d ago First seen · 6 lines · 21 tokens per session scan A b6aae936a1ee
no-unnecessary-updates-rule is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (234 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 35 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-commenting-standards, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
04-review-and-commit
Review, completion, and commit workflow.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
git-commit
Use this when the user asks for a git commit, commit message, or commit command.
02-documentation-workflow
Documentation-driven development workflow.
changelog-generator-manual
This rule generates a comprehensive changelog.md file by analyzing all git tags and commits, creating a chronological record of all project changes with proper semantic versioning structure. The changelog.md file is stored at the root of the project.