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/cmnemoi/cursor-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/cmnemoi/cursor-rules/7-testing-backend-php)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/7-testing-backend-php"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/7-testing-backend-php/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/cmnemoi/cursor-rules/7-testing-backend-php"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/7-testing-backend-php.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.00000 | $0.00286 |
| Opus 5.5 | $0.00000 | $0.00114 |
| Sonnet 5.5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00029 |
Grade A, and why
7-testing-backend-php 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
Test Organization:
- Name test classes with
Testsuffix for unit tests,Cestfor functional tests - Follow
test[Should|Can|Will]DoSomethingmethod naming - Place tests in matching domain structure
- Group related tests by behavior
- Test real behaviors, not implementation details
Test Structure:
- Use
Given-When-Thenpattern in method names - Extract test steps into
givenXxx(),whenXxx(),thenXxx() - Setup common test data in
setUp()(Codeception) or_before()(PHPUnit) - Keep tests independent and idempotent
- Test both success and failure paths
Test Data:
- Use in-memory repositories over mocks
- Create test data in setup methods
- Use factories for test entities
- Inject dependencies via constructor
- Reset state between tests via setup methods
Assertions:
- Assert one behavior per test
- Use descriptive assertion methods
- Keep assertions minimal and focused
- Verify outcomes, not implementation
- Test edge cases and error paths
Test Doubles:
- Only external dependencies should be replace by test doubles, by implementing interfaces
- Prefer stubs and fakes to replace dependencies
- Use spies to verify interactions only if necessary
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 · 39 lines · 286 tokens per session scan A da193bd1762c
7-testing-backend-php 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 286 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
hatch3r-php-laravel-patterns
PHP 8.3+ and Laravel 11.x conventions covering typed properties, attributes, Eloquent ORM, Service Container DI, Pest testing, queue workers, and Laravel Pint formatting.
phpunit-test
PHPUnit testing best practices for PHP applications.
pest-test
Cursor rule "pest-test" from joaopaulolndev/cursor-rules-skills-subagents-commands, covering pest testing, when to use and keywords.
pest-multi-auth
Pest Multi Auth Guard Testing.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
laravel
Definitive guide for writing clean, performant, and secure Laravel applications, emphasizing modern best practices and common pitfalls.