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.
npx agentmods add rules/jakerains/citrusrules/error-handlinggit clone --depth 1 https://github.com/jakerains/CitrusRulesWhat 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 | $0.00000 | $0.02316 |
| Opus 5 | $0.00000 | $0.01158 |
| Sonnet 5 | $0.00000 | $0.00463 |
| Haiku 4.5 | $0.00000 | $0.00232 |
Grade A, and why
error-handling scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
const response = await fetch(url, { How it starts
The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.
name: ErrorHandlingStandards type: Auto Attached description: Enforce comprehensive error handling patterns, custom error types, and robust failure recovery mechanisms across all code implementations glob: **/*.{js,ts,tsx,jsx,py,java,go,rb,php,swift,kt} priority: high
Error Handling Standards
Implement robust, typed error handling with proper abstraction levels, meaningful messages, and comprehensive recovery mechanisms. This rule ensures consistent error handling patterns across the entire codebase.
Core Error Handling Principles
When writing any code, I will:
- Fail Fast with Context: Detect and report errors immediately with rich contextual information
- Type-Safe Error Handling: Use typed errors instead of generic Error objects
- Proper Abstraction: Handle errors at the appropriate level in the application architecture
- Never Silence: Always handle errors explicitly - never swallow them without proper logging/recovery
- Graceful Degradation: Implement fallback mechanisms for critical functionality
- User-Friendly Messages: Provide clear, actionable error messages for users
Implementation Patterns
1. Custom Error Classes Architecture
Always implement a structured error hierarchy:
// Base error class with required properties
abstract class AppError extends Error {
abstract readonly code: string;
abstract readonly statusCode: number;
abstract readonly severity: 'low' | 'medium' | 'high' | 'critical';
constructor(
message: string,
public readonly context?: Record<string, unknown>,
public readonly userMessage?: string
) {
super(message);
this.name = this.constructor.name;
Error.captureStackTrace(this, this.constructor);
}
toJSON() {
return {
name: this.name,
message: this.message,
code: this.code,
statusCode: this.statusCode,
severity: this.severity,
context: this.context,
userMessage: this.userMessage
};
}
}
// Specific error implementations
class ValidationError extends AppError {
readonly code = 'VALIDATION_ERROR';
readonly statusCode = 400;
readonly severity = 'medium' as const;
}
class NotFoundError extends AppError {
readonly code = 'NOT_FOUND';
readonly statusCode = 404;
readonly severity = 'low' as const;
}
class DatabaseError extends AppError {
readonly code = 'DATABASE_ERROR';
readonly statusCode = 500;
readonly severity = 'high' as const;
}
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.
- 2d ago First seen · 383 lines · 0 tokens per session scan A c41d2266cd5d
error-handling is a cursor rule published in the GitHub repository jakerains/CitrusRules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,316 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.