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/shumatsumonobu/awesome-ai-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/shumatsumonobu/awesome-ai-rules/testing)<a href="https://agentmods.dev/rules/shumatsumonobu/awesome-ai-rules/testing"><img src="https://agentmods.dev/badge/rules/shumatsumonobu/awesome-ai-rules/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/shumatsumonobu/awesome-ai-rules/testing"><img src="https://agentmods.dev/badge/rules/shumatsumonobu/awesome-ai-rules/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.00020 | $0.00246 |
| Opus 5.5 | $0.00008 | $0.00098 |
| Sonnet 5.5 | $0.00004 | $0.00049 |
| Haiku 4.5 | $0.00002 | $0.00025 |
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 2mo 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 Rules (agent-requested)
No globs, no alwaysApply. The AI reads this file's DESCRIPTION and decides to pull it in when the task involves writing or modifying tests -- even if you're not viewing a test file.
Example: you say "add tests for the UserCard component" while viewing UserCard.tsx. The agent sees the description mentions "testing conventions" and loads this file automatically.
Stack
- Vitest + React Testing Library + @testing-library/user-event
Patterns
- Test behavior, not implementation. Query by role, text, or label.
- Use
screen.getByRole()overscreen.getByTestId(). - Use
userEventfor interactions, notfireEvent. - Mock Server Actions and API calls. Never hit real endpoints.
- Use factory functions for test data, not inline object literals.
File Location
- Co-locate:
Button.test.tsxnext toButton.tsx. - Integration tests in
__tests__/at the feature root.
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.
- 2mo ago First seen · 29 lines · 20 tokens per session scan A a9ccc0d826b9
testing is a cursor rule published in the GitHub repository shumatsumonobu/awesome-ai-rules (1 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 246 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
jest-unit-testing-cursorrules-prompt-file
Cursor rules for Jest development with unit testing.
python-cursorrules-prompt-file-best-practices
Cursor rules for Python development with best practices integration.
go
Idiomatic Go rules. Explicit error handling, interface-based design, context-first concurrency.
rails-cursorrules-prompt-file
Cursor rules for Rails development with basic setup.
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
react-query-tests
// ✅ CORRECT: Legacy React Query pattern const ctx = konn() .beforeEach(() => createAppRouter()) .afterEach((ctx) => ctx?.close?.()) .done().