What is 302-agent-error-recovery?

A set of rules for recovering from common coding-agent errors, such as edit conflicts, failed tests, incomplete file writes, and race conditions.

It helps with safe file edits, test-failure recovery, multi-file rollback, and coordinating operations that must happen one at a time.

It gives the agent a consistent way to retry work, restore backups, and avoid leaving files damaged after a failed operation.

302-agent-error-recovery — Cursor rule for Cursor by hamzaamjad

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/hamzaamjad/cursor-rules

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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/302-agent-error-recovery/github.svg)](https://agentmods.dev/rules/hamzaamjad/cursor-rules/302-agent-error-recovery)

Your own site

<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/302-agent-error-recovery"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/302-agent-error-recovery/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/302-agent-error-recovery"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/302-agent-error-recovery.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 7 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 304 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00007	$0.00304
Opus 5.5	$0.00003	$0.00122
Sonnet 5.5	$0.00001	$0.00061
Haiku 4.5	$0.00001	$0.00030

Measured 1mo ago against content hash 8aaa9279cac5, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

302-agent-error-recovery 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.

rules/300-integration/302-agent-error-recovery.mdc · 45 lines

What it actually says

Agent Error Recovery

Common Failures & Fixes

Error	Detection	Recovery
Edit conflict	"Content not found"	Re-read → Retry with fresh content
Test failure	Exit code ≠ 0	Analyze output → Fix → Retest
Partial write	Truncated file	Restore backup → Chunk smaller
Race condition	Unexpected state	Lock file → Sequential ops

Recovery Patterns

def safe_edit_with_retry(path, changes, max_attempts=3):
    for attempt in range(max_attempts):
        try:
            current = read_file(path)
            backup = create_backup(path)
            result = edit_file(path, changes)
            if verify_changes(path, expected):
                return result
        except EditError as e:
            restore_backup(backup)
            if attempt == max_attempts - 1:
                raise
            changes = adapt_changes(e, current)

Rollback Strategy

Always backup before destructive ops
Use git stash for complex changes
Implement undo log for multi-file edits
Test rollback path in dry-run mode

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.

1mo ago First seen · 45 lines · 7 tokens per session scan A 8aaa9279cac5

Subscribe to this mod's changes

302-agent-error-recovery is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 304 once invoked, about $0.0000 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.

Debugging

error-handling-and-validation

A code-quality guide for handling errors, invalid inputs, edge cases, preconditions, logging, and user-friendly error messages.

holtwood/awesome-cursorrules-zh · 185 tokens

css-render-blocking-diagnosis

Cursor rule "css-render-blocking-diagnosis" from adobecom/da-express-milo, covering css render-blocking diagnosis & resolution, critical learning from 98 pagespeed achievement, primary diagnostic protocol, step 1: css blocking symptom recognition and step 2: css loading sequence audit.

adobecom/da-express-milo · 1,102 tokens

302-agent-error-recovery