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/error-handling-priorities)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/error-handling-priorities"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/error-handling-priorities/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/error-handling-priorities"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/error-handling-priorities.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.00147 |
| Opus 5.5 | $0.00000 | $0.00059 |
| Sonnet 5.5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00015 |
Grade A, and why
error-handling-priorities 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.
What it actually says
- 在函数开头处理错误和边缘情况。
- 对错误条件使用提早返回，以避免深度嵌套的 if 语句。
- 将"快乐路径"（正常执行路径）放在函数末尾，以提高可读性。
- 避免不必要的 else 语句；改用 if-return 模式。
- 使用卫语句（guard clauses）尽早处理前置条件和无效状态。
- 实现适当的错误日志记录和用户友好的错误消息。
- 使用自定义错误类型或错误工厂以实现一致的错误处理。
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 · 13 lines · 0 tokens per session scan A 0919a99c96af
error-handling-priorities is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (240 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 147 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
network-troubleshoot
Systematic, safety-first network troubleshooting for developers.
qa-bug-report-cursorrules-prompt-file
Cursor rules for QA development with bug report integration.
playwright-defect-tracking-cursorrules-prompt-file
Cursor rules for Playwright development with defect tracking.
python-developer-cursorrules-prompt-file
Cursor rules for Python development with developer 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.