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/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/nodebench-agentic-reliability)<a href="https://agentmods.dev/rules/homenshum/nodebenchai/nodebench-agentic-reliability"><img src="https://agentmods.dev/badge/rules/homenshum/nodebenchai/nodebench-agentic-reliability/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/homenshum/nodebenchai/nodebench-agentic-reliability"><img src="https://agentmods.dev/badge/rules/homenshum/nodebenchai/nodebench-agentic-reliability.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.00000 | $0.00245 |
| Opus 5.5 | $0.00000 | $0.00098 |
| Sonnet 5.5 | $0.00000 | $0.00049 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
nodebench-agentic-reliability 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.
What it actually says
NodeBench: Agentic Reliability Checklist
Run this 8-point checklist on every backend/infra change that agents interact with.
The 8 Checks
- BOUND — Every in-memory collection has MAX size + eviction
- HONEST_STATUS — No 2xx on failure paths
- HONEST_SCORES — No hardcoded score floors
- TIMEOUT — AbortController + budget gates on every external call
- SSRF — URL validation before fetch
- BOUND_READ — Response size caps on external bodies
- ERROR_BOUNDARY — Async error handling on all routes
- DETERMINISTIC — Sorted-key hashing for content-addressed storage
Severity
- P0: Crash, SSRF, false data — Fix immediately
- P1: Degraded data, no crash — Fix same session
- P2: Suboptimal but safe — Fix when touched
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 · 27 lines · 0 tokens per session scan A 9eaea705c6bd
nodebench-agentic-reliability is a cursor rule published in the GitHub repository HomenShum/NodeBenchAI (15 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 245 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-09-03.
Other cursor rules, from other repositories
hatch3r-observability-logging
Structured logging and error reporting conventions for the project.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.