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/hamzaamjad/cursor-rules/302-agent-error-recoverygit clone --depth 1 https://github.com/hamzaamjad/cursor-rulesWrote 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/hamzaamjad/cursor-rules/302-agent-error-recovery)<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="Measured on agentmods" 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 | $0.00007 | $0.00304 |
| Opus 5 | $0.00003 | $0.00152 |
| Sonnet 5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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 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.
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
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.
- 3d ago First seen · 45 lines · 7 tokens per session scan A 8aaa9279cac5
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. 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
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.