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/scenario_testinggit clone --depth 1 https://github.com/HomenShum/NodeBenchAIWhat 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.00837 |
| Opus 5 | $0.00000 | $0.00418 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
scenario_testing 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 2d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Scenario-Based Testing
Tests that don't model real human behavior are false confidence — not test coverage.
Core mandate
Never write simple tests. Every test must be scenario-based: start from a real user context, simulate realistic behavior, and verify system behavior under that context at scale.
"Do not go for simple tests — they are not able to truly address how real people's behavior is going to show up during production. Tests must always be scenario-based, catered and aligned with real human behaviors in all angles. Do not go shallow — they must go thoroughly, deeply, and must consider scale. They must consider long-running and short-running."
What "scenario-based" means
Every test must answer all six of these:
- Who — Which user persona? (first-timer, power user, distracted, adversarial, mobile/slow network, concurrent session)
- What — What is the user trying to achieve? (start from goal, not function signature)
- How — What is the action sequence, timing, and concurrency pattern?
- Scale — What happens at 1 user, 10 concurrent, 100 sustained? Single-user happy paths are necessary but not sufficient.
- Duration — Short-running (burst, spike) AND long-running (sustained load, state accumulation, memory leak over time). A test that passes in 1 second but fails after 30 minutes is a production gap.
- Failure modes — Edge cases, race conditions, degraded inputs, partial failures, auth expiry mid-flow, retry storms.
Required test categories per feature
| Category | What it covers |
|---|---|
| Single user — happy path | Baseline correctness |
| Single user — all sad paths | Every error condition, invalid input, boundary value |
| Concurrent users | Race conditions, dirty reads, double-submit |
| Degraded conditions | Slow network, auth expiry, partial API failures, quota exhaustion |
| Long-running accumulation | State after 100+ sessions, memory/DB growth, stale cache eviction |
| Adversarial | Injection, unexpected payloads, replay attacks on idempotent operations |
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.
- 2d ago First seen · 73 lines · 0 tokens per session scan A 058d4d300aa0
scenario_testing is a cursor rule published in the GitHub repository HomenShum/NodeBenchAI (14 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 837 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.
conservative-file-creation
Check for existing files before creating. Be conservative about new files and code.
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.