error-handling

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

A set of coding rules for handling errors with typed error categories, clear boundaries, safe user messages, logging, and consistent API responses. An API is a way for software components to exchange requests and results.

In plain words
What is it for?
Use it to design error types and responses, translate low-level failures into domain-specific errors, handle UI failures, log unexpected errors, and support retries and recovery.
Why use it?
It helps distinguish expected problems, such as invalid input or a timeout, from programming bugs, while preserving useful information for users and developers.

Cursor rule for Cursor

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

Good fit Use it to design error types and responses, translate low-level failures into domain-specific errors, handle UI failures, log unexpected errors, and support retries and recovery.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/nedcodes-ok/cursor-doctor/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/cursor-doctor

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/cursor-doctor/error-handling/github.svg)](https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/error-handling)
Your own site
<a href="https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/error-handling"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/error-handling/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.

agentmods 80×15 button for error-handling

Your own site · 80×15
<a href="https://agentmods.dev/rules/nedcodes-ok/cursor-doctor/error-handling"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursor-doctor/error-handling.svg" alt="Reviewed on agentmods" width="80" 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 100% copy Near-identical to another mod 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.5 $0.00197 $0.00197
Sonnet 5.5 $0.00099 $0.00099
Haiku 4.5 $0.00049 $0.00049

Measured 1mo ago against content hash 049e57711eb4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

100% identical to error-handling — 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.

pro-kit/templates/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. 1mo 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/cursor-doctor (9 stars, last pushed 7mo ago), licensed MIT. It adds 493 tokens to every session, about $0.0020 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to error-handling, differing in 0 lines, and is treated as a copy.