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/samplexbro/agentsmesh/testinggit clone --depth 1 https://github.com/sampleXbro/agentsmeshWrote 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/samplexbro/agentsmesh/testing)<a href="https://agentmods.dev/rules/samplexbro/agentsmesh/testing"><img src="https://agentmods.dev/badge/rules/samplexbro/agentsmesh/testing.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.00061 |
| Opus 5 | $0.00000 | $0.00030 |
| Sonnet 5 | $0.00000 | $0.00012 |
| Haiku 4.5 | $0.00000 | $0.00006 |
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 yesterday.
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
- Use Vitest.
- Test the user-visible behavior before implementation details.
- Prefer one regression case per bug fix instead of broad snapshot churn.
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.
- yesterday First seen · 13 lines · 0 tokens per session scan A 114de1a85e00
testing is a cursor rule published in the GitHub repository sampleXbro/agentsmesh (24 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 61 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
mock-patterns
Mock and test fixture patterns for consistent testing.
testing-standards
Testing standards and patterns for all code.
testing-patterns
Testing patterns and best practices for PRPM codebase with Vitest.
vitest-config
Shared @repo/vitest-config factories - dual entries, Turbo package caching, Node vs Workers knobs.
front-react
Front-app Vitest - Node pool only, isolated QueryClient, no Workers pool.
testing
Vitest testing discipline - trust boundaries, no weakening source to pass tests.