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/general-assistant-rules)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/general-assistant-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/general-assistant-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/general-assistant-rules"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/general-assistant-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.00182 | $0.00182 |
| Opus 5.5 | $0.00073 | $0.00073 |
| Sonnet 5.5 | $0.00036 | $0.00036 |
| Haiku 4.5 | $0.00018 | $0.00018 |
Grade A, and why
general-assistant-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 — 12 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 · 12 lines · 182 tokens per session scan A 64b4c92cb97c
general-assistant-rules is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (239 stars, last pushed 6d ago), licensed MIT. It adds 182 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 12 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
vscode
VS Code: settings, extensions, workspace config.
file-organization
Maintain perfect project organization. Never create files in wrong locations.
automation-script-rule
Sets guidelines for creating or modifying automation scripts within the project.
no-implementation-checks-rule
description: This rule prevents the AI from asking the user to verify implementations that are visible in the provided context. globs: /.