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/2-php-naming-conventions)<a href="https://agentmods.dev/rules/cmnemoi/cursor-rules/2-php-naming-conventions"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/2-php-naming-conventions/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/2-php-naming-conventions"><img src="https://agentmods.dev/badge/rules/cmnemoi/cursor-rules/2-php-naming-conventions.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.00272 |
| Opus 5.5 | $0.00000 | $0.00109 |
| Sonnet 5.5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
2-php-naming-conventions 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
Classes:
- Use PascalCase for class names
- Use nouns or noun phrases
Interfaces and Traits:
- Use PascalCase for names
- Suffix interfaces with
Interface - Suffix traits with
Trait
Methods and Functions:
- Use camelCase for names
- Use verbs for actions
- Use nouns for value-returning methods
- Prefix boolean-returning methods with
is,has, orshould - Use type declarations for parameters and return types
Properties and Variables:
- Use camelCase for names
- Declare visibility explicitly (
private,protected,public) - Use type declarations for properties
- Use constructor property promotion for dependency injection
Constants and Enums:
- Use UPPER_SNAKE_CASE for enum cases
- Group related constants in enum classes with descriptive names
Namespaces:
- Use PascalCase for namespace segments
- Organize by domain concepts
- Follow PSR-4 autoloading standard
File Names:
- Match class name exactly including case
- One class per file
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 · 42 lines · 272 tokens per session scan A e8efc4e88bda
2-php-naming-conventions 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 272 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
laravel
Definitive guide for writing clean, performant, and secure Laravel applications, emphasizing modern best practices and common pitfalls.
laravel-package-coding-standards
A set of coding rules for Laravel packages, with conventions for names and code across several development areas.
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.
backend
Essential backend patterns and commands for PHP/Symfony.
php
Rules applied when working in PHP files (incl. Laravel, Symfony, WordPress).
coding-style
Project-specific PHP quality checks.