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/mitas/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/mitas/cursor-rules/php)<a href="https://agentmods.dev/rules/mitas/cursor-rules/php"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/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/mitas/cursor-rules/php"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/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.01840 |
| Opus 5.5 | $0.00000 | $0.00736 |
| Sonnet 5.5 | $0.00000 | $0.00368 |
| Haiku 4.5 | $0.00000 | $0.00184 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PHP Coding Standards and Best Practices
Overview
This document outlines the coding standards and best practices for PHP development, focusing on modern PHP principles applicable across PHP versions 7.4 and later.
Code Style
Naming Conventions
- Classes: Use PascalCase (e.g.,
UserProfile,DatabaseConnection) - Methods/Functions: Use camelCase (e.g.,
getUserData(),connectToDatabase()) - Variables: Use camelCase (e.g.,
$userData,$databaseConfig) - Constants: Use UPPERCASE with underscores (e.g.,
MAX_LOGIN_ATTEMPTS,DEFAULT_TIMEOUT) - Private/Protected Properties: Prefix with underscore (e.g.,
$_privateProperty) - Namespaces: Use PascalCase (e.g.,
App\Services\Authentication) - Interfaces: Suffix with Interface (e.g.,
RepositoryInterface,CacheInterface) - Traits: Suffix with Trait (e.g.,
LoggableTrait,SerializableTrait) - Abstract Classes: Prefix with Abstract (e.g.,
AbstractController,AbstractRepository)
Code Formatting
- Use 4 spaces for indentation, not tabs
- Line length should generally not exceed 120 characters
- Use one blank line to separate logical blocks of code
- Place opening braces on the same line for control structures
- Place opening braces on the next line for classes and methods
- Include a space after control structure keywords and before parentheses
- Use explicit visibility (
public,protected, orprivate) for class methods and properties - Use trailing commas in multiline arrays
- Avoid unnecessary parentheses
// Good
if ($condition) {
// code
} else {
// code
}
// Good
public function methodName($param1, $param2)
{
// Method body
}
// Good
$array = [
'key1' => 'value1',
'key2' => 'value2',
];
PHP Standards
Use Modern PHP Features
- Prefer type declarations (scalar types, return types, nullable types)
- Use native PHP functions over custom implementations when available
- Use appropriate data structures (arrays, objects, generators)
- Leverage PHP's built-in array functions (
array_map,array_filter, etc.) - Use anonymous functions and arrow functions for simple callbacks
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 · 242 lines · 1,840 tokens per session scan A 0dad94b9f045
php is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,840 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.