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/abderrahimghazali/cursor-rules/php-drupal-best-practicesgit clone --depth 1 https://github.com/abderrahimghazali/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.05115 |
| Opus 5 | $0.00000 | $0.02558 |
| Sonnet 5 | $0.00000 | $0.01023 |
| Haiku 4.5 | $0.00000 | $0.00511 |
Grade A, and why
php-drupal-best-practices 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 2d 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Enhanced PHP & Drupal Development Standards
Defines comprehensive coding standards and best practices for PHP and Drupal development, with a focus on modern PHP features, Drupal 10+ standards, and modularity.
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: "(?<!\bTRUE\b)\btrue\b|(?<!\bFALSE\b)\bfalse\b|(?<!\bNULL\b)\bnull\b" message: "Use uppercase for TRUE, FALSE, and NULL constants."
-
pattern: "(?i)\/\/\s[a-z]" message: "Ensure inline comments begin with a capital letter and end with a period."
-
pattern: "class\s+\w+\s*(?!\{[^}]*readonly\s+\$)" message: "Consider using readonly properties where immutability is required."
-
pattern: "public\s+function\s+\w+\([^)]\)\s(?!:)" message: "Add return type declarations for all methods to ensure type safety."
-
pattern: "extends\s+\w+\s*\{[^}]public\s+function\s+\w+\([^)]\)\s*(?!#\[Override\])" message: "Add #[Override] attribute for overridden methods for clarity."
-
pattern: "\$\w+\s*(?!:)" message: "Use typed properties with proper nullability for better code maintainability."
-
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: "function\s+\w+\s*\([^)]\)\s\{[^}]*\$this->t\(" message: "Use Drupal's t() function for strings that need translation."
-
pattern: "\$this->config\('\w+'\)" message: "Use ConfigFactory for configuration management."
-
pattern: "array\s*\(" message: "Use short array syntax ([]) instead of array() for consistent code style."
-
pattern: "(?<!\()\s+\(int\)\s*\$" message: "Put a space between the (type) and the $variable in a cast: (int) $mynumber."
-
pattern: "\n[\t ]+\n" message: "Remove whitespace from empty lines."
-
pattern: "\s+$" message: "Remove trailing whitespace at the end of lines."
-
pattern: "^(?!.*\n$)" message: "Ensure files end with a single newline character."
-
pattern: "if\s*\([^)]\)\s\{[^{]\}\selse\s*\{" message: "Place the opening brace on the same line as the statement for control structures."
-
pattern: "\$_GET|\$_POST|\$_REQUEST" message: "Never use superglobals directly; use Drupal's input methods."
-
pattern: "mysql_|mysqli_" message: "Use Drupal's database API instead of direct MySQL functions."
-
pattern: "\t+" message: "Use 2 spaces for indentation, not tabs."
-
pattern: "function\s+\w+\s*\([^)]\)\s\{[^}]*\becho\b" message: "Don't use echo; use return values or Drupal's messenger service."
-
pattern: "(?<!\/\\)\s*\*\s+@" message: "Use proper DocBlock formatting for documentation."
-
pattern: "\bdie\b|\bexit\b" message: "Don't use die() or exit(); throw exceptions instead."
-
pattern: "\$entity->get\([^)]+\)->getValue\(\)" message: "Use $entity->get('field_name')->value instead of getValue() when possible."
-
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.
- 2d ago First seen · 501 lines · 5,115 tokens per session scan A 55435af46128
php-drupal-best-practices is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 5,115 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
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
cursorrules
You are a disciplined senior engineer working with someone who may be a domain expert, not a programmer. Build it correctly and safely, not just fast.
cursorrules
Cursor rule "cursorrules" from BlueBirdBack/godot-cursorrules, covering godot 4.4 game development .cursorrules, core development guidelines, code style, naming conventions and scene organization.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.