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/ivangrynenko/cursorrules/drupal-security-misconfigurationgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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.01510 |
| Opus 5 | $0.00000 | $0.00755 |
| Sonnet 5 | $0.00000 | $0.00302 |
| Haiku 4.5 | $0.00000 | $0.00151 |
Grade A, and why
drupal-security-misconfiguration 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Security Misconfiguration Standards (OWASP A05:2021)
This rule enforces security best practices to prevent misconfiguration vulnerabilities in Drupal applications, as defined in OWASP Top 10:2021-A05.
Rule Details
-
Name: drupal_security_misconfiguration
-
Description: Detect and prevent security misconfigurations in Drupal as defined in OWASP Top 10:2021-A05
Filters
- file extension pattern:
\\.(php|inc|module|install|theme|yml|info\\.yml)$ - file path pattern:
.*
Enforcement Checks
- Conditions:
- pattern
\\$settings\\['update_free_access'\\]\\s*=\\s*TRUE|\\$settings\\['cache'\\]\\s*=\\s*FALSE|\\$settings\\['rebuild_access'\\]\\s*=\\s*TRUE|\\$config\\['system\\.performance'\\]\\['cache'\\]\\s*=\\s*FALSE– Development settings detected in production code. Ensure these settings are only enabled in development environments.- Pattern 1: Development settings in production code
- pattern
settings\\.php|settings\\.local\\.php– Verify that $settings['trusted_host_patterns'] is properly configured to prevent HTTP Host header attacks.- Pattern 2: Missing or weak trusted host patterns
- pattern
\\$config\\['system\\.logging'\\]\\['error_level'\\]\\s*=\\s*'verbose'|ini_set\\('display_errors'\\s*,\\s*'1'\\)|error_reporting\\(E_ALL\\)– Error display should be disabled in production. Use 'hide' for error_level in production.- Pattern 3: Debugging/error display enabled
- pattern
\\$settings\\['file_chmod_directory'\\]\\s*=\\s*0777|\\$settings\\['file_chmod_file'\\]\\s*=\\s*0666– Excessively permissive file permissions detected. Use more restrictive permissions.- Pattern 4: Insecure file permissions settings
- pattern
\\.htaccess|sites/default/default\\.settings\\.php– Ensure Content-Security-Policy headers are properly configured to prevent XSS attacks.- Pattern 5: Disabled or misconfigured CSP headers
- pattern
session\\.cookie_secure\\s*=\\s*0|session\\.cookie_httponly\\s*=\\s*0|\\$settings\\['cookie_secure_only'\\]\\s*=\\s*FALSE– Session cookies should be secure and HTTP-only in production environments.- Pattern 6: Insecure session cookie settings
- pattern
settings\\.php– Ensure $settings['file_private_path'] is properly configured for storing sensitive files.- Pattern 7: Missing or misconfigured private file path
- pattern
core\\.extension\\.yml– Check for development modules (devel, webprofiler, etc.) that should not be enabled in production.- Pattern 8: Development modules enabled in production
- pattern
function\\s+[a-zA-Z0-9_]+_install\\(\\)– Remove or secure default/demo content and users in production environments.- Pattern 9: Default or demo content in production
- pattern
\\.htaccess|nginx\\.conf– Verify X-Frame-Options, X-Content-Type-Options, X-XSS-Protection, and Referrer-Policy headers are properly configured.- Pattern 10: Missing or misconfigured security headers
- pattern
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 · 98 lines · 1,510 tokens per session scan A 871394221e2e
drupal-security-misconfiguration is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (87 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,510 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-30.
Other cursor rules, from other repositories
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.