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/movahedan/monobunWrote 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/movahedan/monobun/testing)<a href="https://agentmods.dev/rules/movahedan/monobun/testing"><img src="https://agentmods.dev/badge/rules/movahedan/monobun/testing/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/movahedan/monobun/testing"><img src="https://agentmods.dev/badge/rules/movahedan/monobun/testing.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.00367 | $0.00367 |
| Opus 5.5 | $0.00147 | $0.00147 |
| Sonnet 5.5 | $0.00073 | $0.00073 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
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 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
Testing
Stack (configured — do not restate)
- Runner:
bun:test— seebunfig.tomlpreload - Preset:
tools/tests-preset— HappyDOM, Testing Library, cleanup - Details:
tools/tests-preset/AGENTS.md
Naming and structure
describe('<module> - <unit>', () => {})it('<expected outcome> when <condition>', () => {})- No inline comments or JSDoc in tests; names document behavior
- AAA layout; blank line between logical groups inside a test
Quality bar
- Assert observable behavior, not internals
- One failure reason per test; no flakiness (mock time/network/random)
- Mock boundaries only (network, DB, fs, env) — not pure logic
- Restore spies; preset handles most cleanup
File placement
- Unit:
src/<area>/<thing>.test.tsorsrc/__tests__/ - Integration:
src/__tests__/<thing>.integration.test.ts
Patterns
- Table-driven cases via
cases.forEachortest.each(Bun:test.each/describe.each, notit.each)
Commands
See docs/CHEATSHEET.md — bun test, bun run overall.
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 · 41 lines · 367 tokens per session scan A 259ea034716f
testing is a cursor rule published in the GitHub repository movahedan/monobun (18 stars, last pushed 3d ago), licensed MIT. It adds 367 tokens to every session, about $0.0015 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-30.
Other cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.