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-logging-failuresgit 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.01494 |
| Opus 5 | $0.00000 | $0.00747 |
| Sonnet 5 | $0.00000 | $0.00299 |
| Haiku 4.5 | $0.00000 | $0.00149 |
Grade A, and why
drupal-logging-failures 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Security Logging and Monitoring Failures Standards (OWASP A09:2021)
This rule enforces security best practices to prevent logging and monitoring failures in Drupal applications, as defined in OWASP Top 10:2021-A09.
Rule Details
-
Name: drupal_logging_failures
-
Description: Detect and prevent security logging and monitoring failures in Drupal as defined in OWASP Top 10:2021-A09
Filters
- file extension pattern:
\\.(php|inc|module|install|theme|yml)$ - file path pattern:
.*
Enforcement Checks
- Conditions:
- pattern
(delete|update|create|execute|grant|revoke|config|schema).*function[^}]*\\{(?![^}]*(log|watchdog|logger))– Critical operations should include logging. Implement proper logging for security-relevant actions.- Pattern 1: Missing critical event logging
- pattern
@include|@require|@eval|error_reporting\\(0\\)|ini_set\\(['\"](mdc:display_errors|log_errors)['\"],\\s*['\"]0['\"]\\)– Avoid suppressing errors and warnings. Implement proper error handling and logging instead.- Pattern 2: Suppressed error logging
- pattern
catch\\s*\\([^{]*\\)\\s*\\{(?![^}]*log|[^}]*watchdog|[^}]*logger)– Exceptions should be properly logged, especially in security-critical sections.- Pattern 3: Improper exception handling without logging
- pattern
dblog\\.settings\\.yml|syslog\\.settings\\.yml|logging\\.settings\\.yml– Ensure logging is properly configured and not disabled. Verify log verbosity and retention policies.- Pattern 4: Disabled watchdog
- pattern
(login|authenticate|logout|password).*function[^}]*\\{(?![^}]*(log|watchdog|logger))– Authentication events should always be logged for security monitoring and auditing.- Pattern 5: Missing authentication event logging
- pattern
AccessResult::(allowed|forbidden|neutral)\\([^)]*\\)(?![^;]*(log|watchdog|logger))– Consider logging significant access control decisions, especially denials, for security monitoring.- Pattern 6: Failure to log access control decisions
- pattern
(file_save|file_delete|file_move|file_copy)[^;]*;(?![^;]*(log|watchdog|logger))– File operations should be logged, especially for security-sensitive files.- Pattern 7: Missing logging in file operations
- pattern
(\\->log|watchdog)\\([^,)]*,[^,)]*\\)– Log messages should include sufficient context and detail for effective security monitoring.- Pattern 8: Insufficient detail in log messages
- pattern
\\$config->set\\([^;]*;(?![^;]*(log|watchdog|logger))– Configuration changes should be logged to maintain an audit trail and detect unauthorized changes.- Pattern 9: Failure to log configuration changes
- pattern
class\\s+[a-zA-Z0-9_]+Resource.+\\{[^}]*function\\s+[a-zA-Z0-9_]+\\([^{]*\\)\\s*\\{(?![^}]*(log|watchdog|logger))– API endpoint access should be logged for security monitoring, especially for sensitive operations.- Pattern 10: Missing logs for API access
- 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 · 105 lines · 1,494 tokens per session scan A 66ef8b37eab4
drupal-logging-failures 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,494 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.