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/ivangrynenko/cursorrulesWrote 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/ivangrynenko/cursorrules/php-drupal-development-standards)<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/php-drupal-development-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/php-drupal-development-standards/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/ivangrynenko/cursorrules/php-drupal-development-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/php-drupal-development-standards.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.01070 |
| Opus 5.5 | $0.00000 | $0.00428 |
| Sonnet 5.5 | $0.00000 | $0.00214 |
| Haiku 4.5 | $0.00000 | $0.00107 |
Grade A, and why
php-drupal-development-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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- php-drupal-development-standards — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced PHP and Drupal Development Standards
Ensures adherence to PHP 8.3+ features and Drupal development best practices for improved code quality, security, and maintainability.
actions:
-
type: enforce conditions:
-
pattern: "^(?!declare\(strict_types=1\);)" message: "Add 'declare(strict_types=1);' at the beginning of PHP files for type safety."
-
pattern: "class\s+\w+\s*(?!\{[^}]*readonly\s+\$)" message: "Consider using readonly properties where immutability is required for better code safety."
-
pattern: "public\s+function\s+\w+\([^)]\)\s(?!:)" message: "Add return type declarations for all methods to enhance type safety."
-
pattern: "extends\s+\w+\s*\{[^}]public\s+function\s+\w+\([^)]\)\s*(?!#\[Override\])" message: "Add #[Override] attribute for overridden methods for clear intent."
-
pattern: "\$\w+\s*(?!:)" message: "Use typed properties with proper nullability to improve code readability and prevent errors."
-
pattern: "function\s+hook_\w+\([^)]\)\s(?!:)" message: "Add type hints and return types for all hooks to leverage PHP's type system."
-
pattern: "new\s+\w+\([^)]\)\s(?!;\s*//\s*@inject)" message: "Use proper dependency injection with services for better testability and modularity."
-
pattern: "extends\s+FormBase\s*\{[^}]*validate" message: "Implement proper form validation in FormBase classes for security."
-
pattern: "(?<!\bTRUE\b)\btrue\b|(?<!\bFALSE\b)\bfalse\b|(?<!\bNULL\b)\bnull\b" message: "Use uppercase for TRUE, FALSE, and NULL constants for consistency."
-
pattern: "(?i)\/\/\s[a-z]" message: "Ensure inline comments begin with a capital letter and end with a period for readability."
-
pattern: "\$this->config\('\w+'\)" message: "Use ConfigFactory for configuration management to ensure proper dependency injection."
-
-
type: suggest message: | PHP/Drupal Development Best Practices:
- File Structure: Place module files in
web/modules/custom/[module_name]/for organization. - Module Files: Ensure modules include .info.yml, .module, .libraries.yml, .services.yml where applicable.
- Dependencies: Use hook_requirements() to manage external dependencies.
- Forms: Use FormBase or ConfigFormBase for creating forms, always include CSRF protection.
- Caching: Apply proper cache tags and contexts for performance optimization.
- Error Handling & Logging: Implement robust error handling and logging using Drupal's mechanisms.
- Type Safety: Leverage type safety in form methods and throughout your code.
- Dependency Injection: Follow Drupal's dependency injection patterns for better maintainability.
- Service Container: Use Drupal's service container to manage dependencies.
- Security: Validate all user inputs, use Drupal's security practices like sanitization and escaping.
- Schema Updates: Implement hook_update_N() for database schema changes.
- Translation: Use Drupal's t() function for all user-facing strings.
- File Structure: Place module files in
-
type: validate conditions:
-
pattern: "web/modules/custom/[^/]+/\.info\.yml$" message: "Ensure each custom module has a required .info.yml file."
-
pattern: "web/modules/custom/[^/]+/\.module$" message: "Ensure module has .module file if hooks are implemented."
-
pattern: "web/modules/custom/[^/]+/src/Form/\w+Form\.php$" message: "Place form classes in the Form directory for consistency."
-
pattern: "try\s*\{[^}]\}\scatch\s*\([^)]\)\s\{\s*\}" message: "Implement proper exception handling in catch blocks for robustness."
-
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 · 87 lines · 1,070 tokens per session scan A c6fe46606e5a
php-drupal-development-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,070 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
laravel
Laravel: Eloquent, Form Requests, policies.
laravel-php-83-cursorrules-prompt-file
Cursor rules for Laravel development with PHP 8.3 integration.
laravel-package-development-guidelines
A set of coding rules for building Laravel packages, which are reusable extensions for Laravel applications. It covers package structure, code style, helper functions, type safety, editor suggestions, and documentation.
laravel-package-coding-standards
A set of coding rules for Laravel packages, with conventions for names and code across several development areas.
laravel-package-structure
A set of coding rules for organising a Laravel package, a reusable extension for Laravel applications.
laravel
Core Laravel architecture and coding conventions.