error-handling

error-handling is a cursor rule for Cursor from nedcodes-ok/cursorrules-collection. It costs 493 tokens per session, scanned A, original, MIT.

A set of rules for representing, handling, and reporting application errors. It distinguishes expected operational problems, such as timeouts, from programming bugs.

In plain words
What is it for?
Use it to define typed errors, translate database or network failures, build consistent API responses, add UI error boundaries, and handle retries.
Why use it?
It gives errors consistent machine codes, safe user messages, useful debugging context, and predictable handling at application boundaries.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

Good fit Use it to define typed errors, translate database or network failures, build…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/nedcodes-ok/cursorrules-collection/error-handling
Install

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.

Clone the repo
git clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collection

Made for: Cursor.

Wrote 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.

agentmods badge for error-handling

README.md
[![agentmods](https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/error-handling.svg)](https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/error-handling)
Your own site
<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/error-handling"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/error-handling.svg" alt="Measured on agentmods" height="20"></a>
Per session 493 This file is loaded in full into every session.
When invoked 493 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00493 $0.00493
Opus 5 $0.00246 $0.00246
Sonnet 5 $0.00099 $0.00099
Haiku 4.5 $0.00049 $0.00049

Measured 3d ago against content hash 049e57711eb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

error-handling 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 3d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

rules-mdc/practices/error-handling.mdc · 50 lines

How it starts

The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Error Handling Cursor Rules

You are an expert at error handling. Follow these rules:

Error Types

  • Distinguish operational errors (expected) from programmer errors (bugs)
  • Operational: invalid input, network timeout, not found — handle gracefully
  • Programmer: null reference, type error, assertion failure — crash and fix
  • Use typed/enumerated errors, not string messages, for programmatic handling
  • Each error needs: code (machine), message (human), context (debugging)

Boundaries

  • Catch errors at module boundaries — dont let implementation details leak
  • Translate low-level errors to domain errors: DBError → UserNotFoundError
  • Unhandled errors bubble to a global handler that logs and returns 500
  • Never catch and ignore. At minimum: log, increment a counter, re-throw
  • Use error boundaries in UI: per-feature, not just root level

Error Responses

  • Consistent error shape across all API endpoints
  • Include error code for client-side handling: "INSUFFICIENT_FUNDS"
  • Human-readable message that is safe to show users
  • Debug details only in development, never in production responses
  • Correlation/request ID in every error for support tracing

Retry & Recovery

  • Retry only idempotent operations and transient failures
  • Exponential backoff with jitter: base * 2^attempt + random jitter
  • Max 3-5 retries. Circuit breaker for persistent failures
  • Timeout every external call. No unbounded waits
  • Graceful degradation: show cached data, disable feature, not blank page

Logging

  • Log errors with full context: user, request, input, stack trace
  • Structured logging: { level, error_code, message, context, stack }
  • Error level for operational failures, fatal for programmer errors
  • Dont log sensitive data in error context (passwords, tokens, PII)

Patterns by Language

  • TypeScript: Result<T, E> pattern or neverthrow library
  • Python: custom exception hierarchy, not bare except
  • Go: errors.Is/As for checking, fmt.Errorf with %w for wrapping
  • Rust: ? operator with custom error enums, thiserror for libraries

Read the full file on GitHub · 50 lines

Changes

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.

  1. 3d ago First seen · 50 lines · 493 tokens per session scan A 049e57711eb4

Subscribe to this mod's changes

error-handling is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0025 per session on Opus 5. 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.