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/andr-ca/agentharnessWrote 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/andr-ca/agentharness/error-handling)<a href="https://agentmods.dev/rules/andr-ca/agentharness/error-handling"><img src="https://agentmods.dev/badge/rules/andr-ca/agentharness/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.
<a href="https://agentmods.dev/rules/andr-ca/agentharness/error-handling"><img src="https://agentmods.dev/badge/rules/andr-ca/agentharness/error-handling.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.00032 | $0.01338 |
| Opus 5.5 | $0.00013 | $0.00535 |
| Sonnet 5.5 | $0.00006 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
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.
How it starts
The opening of the file, as written. The whole thing — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Error Handling & Recovery
Structured approaches to errors, recovery, and observability. Never silently hide errors.
Core Patterns
1. Explicit Errors (Always)
Return errors as values or raise them; never ignore them.
# ✅ Good: Explicit handling
try:
user = parse_user_data(raw)
except json.JSONDecodeError as e:
# Never log the raw payload — it can carry passwords/PII. Log a
# bounded, redaction-safe summary instead.
logger.error("Invalid user JSON", extra={"error": str(e), "payload_length": len(raw)})
return None
# ❌ Bad: Silent failure
try:
parse_user_data(raw)
except:
pass # User data silently ignored
2. Error Wrapping (Across Boundaries)
Add context as errors propagate—original error + where + why.
# ✅ Python: Preserve cause
try:
return repository.find(user_id)
except DatabaseError as e:
raise UserNotFoundError(f"find user {user_id}") from e
# ✅ Go: Wrap with context
user, err := repo.Find(userID)
if err != nil {
return nil, fmt.Errorf("find user %s: %w", userID, err)
}
3. Error Classification
Decide recovery strategy based on error type.
def classify_error(error):
if isinstance(error, (ConnectionError, TimeoutError)):
return "transient" # Retry
elif isinstance(error, (ValueError, KeyError)):
return "validation" # Reject, don't retry
else:
return "unknown"
# Transient → retry with backoff
# Validation → log and fail
# Fatal → panic
4. Retry with Backoff (for Transient Errors)
Retry flaky operations; don't retry permanent failures.
import time
def retry(func, max_attempts=3, backoff_base=2):
"""Retry with exponential backoff."""
for attempt in range(max_attempts):
try:
return func()
except (ConnectionError, TimeoutError) as e:
if attempt < max_attempts - 1:
wait_time = backoff_base ** attempt
logger.warning(f"Retry {attempt + 1}/{max_attempts}, waiting {wait_time}s")
time.sleep(wait_time)
else:
raise
except (ValueError, KeyError):
raise # Don't retry validation errors
# Usage
user = retry(lambda: fetch_user(user_id), max_attempts=3)
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 · 191 lines · 32 tokens per session scan A 1d78ade28f32
error-handling is a cursor rule published in the GitHub repository andr-ca/agentharness (1 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 1,338 once invoked, about $0.0001 per session on Opus 5.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-08-31.
Other cursor rules, from other repositories
root-cause-first
Require source-level fixes for malformed or polluted domain data.
debugging
Debugging discipline. Apply when investigating a bug, test failure, or unexpected behavior.
crew
Crew Mate production-change checklist for one failing target.
windsurfrules
This repo has a GraphPilot structural code-graph available via MCP. Use it before grep on structural questions.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.