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/cmnemoi/cursor-rules/301-testing-standardsgit clone --depth 1 https://github.com/cmnemoi/cursor-rulesWhat 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.00666 |
| Opus 5 | $0.00000 | $0.00333 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
Grade A, and why
301-testing-standards 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing Standards
1.1.0
Context
- These rules apply to all test code in the Mush project
- They ensure consistent implementation of testing patterns
- They promote maintainable, reliable, and behavior-focused test suites
Requirements
Test Organization
- Organize tests by domain/feature in the appropriate directory structure
- Name tests descriptively using "should" statements that describe behavior
- Follow the Given-When-Then pattern in unit tests
- Group related tests by behavior or feature
- Test real user interactions and behaviors, not implementation details
PHP Unit Tests (Api/tests/unit)
- Place tests in directories matching the domain structure (e.g.,
Api/tests/unit/Communications/Service/) - Use TestCase as base class for unit tests
- Use in-memory repositories rather than mocks when possible
- Extract test steps into descriptive methods following Given-When-Then:
givenXxx()for test setupwhenXxx()for executing the behavior under testthenXxx()for assertions
- Test one unit of functionality at a time
- Test both success and failure paths
- Keep assertions focused and minimal
- Use proper test doubles (stubs, fakes, spies) instead of mocks when appropriate
- Test edge cases and error conditions
Codeception Functional Tests (Api/tests/functional)
- Place tests in directories matching the domain structure (e.g.,
Api/tests/functional/Action/Actions/) - Use
Cestsuffix for functional test classes (e.g.,ExchangeBodyCest) - Extend
AbstractFunctionalTestbase class - Set up common test data in
_before()method - Use descriptive test method names with
shouldprefix - Group tests by behavior
- Use explicit step methods for better readability:
givenXxx()for preconditionswhenXxx()for actionsthenXxx()for assertions
- Keep tests independent and idempotent
- Focus on integration between components rather than isolated units
Test Data and Dependencies
- Create test data in the appropriate setup methods
- Use factories for creating test entities
- Use dependency injection for services
- Avoid database fixtures when possible, prefer programmatic setup
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 · 76 lines · 0 tokens per session scan A 8120c89cf1a9
301-testing-standards is a cursor rule published in the GitHub repository cmnemoi/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 666 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-31.
Other cursor rules, from other repositories
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.