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/homenshum/nodebenchai/reexamine_resiliencegit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWrote 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/homenshum/nodebenchai/reexamine_resilience)<a href="https://agentmods.dev/rules/homenshum/nodebenchai/reexamine_resilience"><img src="https://agentmods.dev/badge/rules/homenshum/nodebenchai/reexamine_resilience.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.00000 | $0.00373 |
| Opus 5 | $0.00000 | $0.00187 |
| Sonnet 5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
reexamine_resilience 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
Re-examine: Error Resilience
Retry with backoff
- Network/fetch calls: retry 2-3 times with exponential backoff (
Math.min(30000, base * 1.5^attempt)) - Show retry status to user (e.g., "Retrying in 5s..." or a refresh indicator)
- Add a manual "Retry" button after max retries exhausted
Partial failures
- If one API call in a batch fails, don't discard the successful results
- Render what you have + show targeted error for the failed portion
- Example: 9/10 screenshots load → show 9 + "1 image unavailable" placeholder
Error boundaries (React / UI)
- Wrap major sections in error boundaries so one crash doesn't take down the page
- Error boundary fallback: informative message + retry action, not blank screen
- Log errors to console or telemetry with enough context to debug
Graceful degradation
- If optional dependency missing (embedding model, Python server, env var): degrade, don't crash
- Feature detection before use:
if (window.IntersectionObserver)etc. - Image 404 → fallback placeholder with "Image unavailable" text
- Missing data fields → show "N/A" or hide the section, not
undefined
Loading states
- Every async operation needs a loading indicator (skeleton, spinner, or progress bar)
- Never leave the user staring at a blank screen during fetch
- See
reexamine_polishfor skeleton loading patterns
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 · 34 lines · 373 tokens per session scan A fbed689a0938
reexamine_resilience is a cursor rule published in the GitHub repository HomenShum/NodeBenchAI (14 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 373 tokens. 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-30.
Other cursor rules, from other repositories
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
java-springboot-jpa-cursorrules-prompt-file
description: "Cursor rules for Java development with Springboot and JPA integration." globs: / alwaysApply: false.
executing-red-team-engagement-planning
Red team engagement planning is the foundational phase that defines scope, objectives, rules of engagement (ROE), threat model selection, and operational timelines before any offensive testing begins.
secure-dev-rust
These rules apply to all Rust code in the repository and aim to prevent common security risks through disciplined use of memory safety, input validation, error handling, and safe APIs.
design-patterns
Design patterns (GoF) and file size conventions for sweagent TypeScript codebase.
cursorrules
ALWAYS start your session by reading AGENTS.md and .memory/wiki/hot.md to get project context before suggesting code or answering questions.