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/claire-gong-18/awesome-cursorrulesWrote 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/claire-gong-18/awesome-cursorrules/error-handling-priorities)<a href="https://agentmods.dev/rules/claire-gong-18/awesome-cursorrules/error-handling-priorities"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/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/claire-gong-18/awesome-cursorrules/error-handling-priorities"><img src="https://agentmods.dev/badge/rules/claire-gong-18/awesome-cursorrules/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.00133 | $0.00133 |
| Opus 5 | $0.00067 | $0.00067 |
| Sonnet 5 | $0.00027 | $0.00027 |
| Haiku 4.5 | $0.00013 | $0.00013 |
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 6d 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 error-handling-priorities — 0 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
- Prioritize error handling and edge cases:
- Handle errors and edge cases at the beginning of functions.
- Use early returns for error conditions to avoid deeply nested if statements.
- Place the happy path last in the function for improved readability.
- Avoid unnecessary else statements; use the if-return pattern instead.
- Use guard clauses to handle preconditions and invalid states early.
- Implement proper error logging and user-friendly error messages.
- Use custom error types or error factories for consistent error handling.
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.
- 6d ago First seen · 12 lines · 133 tokens per session scan A 49cd6df21439
error-handling-priorities is a cursor rule published in the GitHub repository claire-gong-18/awesome-cursorrules (0 stars, last pushed 1y ago), licensed CC0-1.0. It adds 133 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to error-handling-priorities, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
python-developer-cursorrules-prompt-file
Cursor rules for Python development with developer integration.
pyright
This guide provides definitive, actionable best practices for configuring and using pyright (and basedpyright) to ensure robust, type-safe Python codebases in 2025.
pylint
Definitive guidelines for configuring and using pylint for deep semantic analysis and code quality in Python projects.
python-code-style-for-apps
Python 3.14 code style for ArchiPy apps — formatting, imports, docstrings, errors, complexity.
mollify
Use Mollify (the mollify CLI / mollify MCP server) as the source of truth for Python dead code and dependency hygiene instead of grep or manual scanning. Agent-Requested.
error-handling-priorities
description: Emphasizes the importance of prioritizing error handling and edge cases in Python code. globs: /.py.