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-authentication-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.01406 |
| Opus 5 | $0.00000 | $0.00703 |
| Sonnet 5 | $0.00000 | $0.00281 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
drupal-authentication-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- drupal-authentication-failures — 86% identical, 216 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Identification and Authentication Failures Standards (OWASP A07:2021)
This rule enforces security best practices to prevent identification and authentication failures in Drupal applications, as defined in OWASP Top 10:2021-A07.
Rule Details
-
Name: drupal_authentication_failures
-
Description: Detect and prevent identification and authentication failures in Drupal as defined in OWASP Top 10:2021-A07
Filters
- file extension pattern:
\\.(php|inc|module|install|theme|yml)$ - file path pattern:
.*
Enforcement Checks
- Conditions:
- pattern
UserPasswordConstraint|PasswordPolicy|user\\.settings\\.yml– Ensure strong password policies are configured to require complexity, length, and prevent common passwords.- Pattern 1: Weak or missing password policies
- pattern
(authenticate|login|auth).*function[^}]*return\\s+(TRUE|true|1)\\s*;– Custom authentication functions should implement proper validation and not return TRUE without checks.- Pattern 2: Custom authentication without proper validation
- pattern
==\\s*\\$password|===\\s*\\$password|strcmp\\(|password_verify\\([^,]+,[^,]+\\$plainTextPassword– Avoid direct password comparison. Use Drupal's built-in password verification services.- Pattern 3: Improper password comparison
- pattern
(username|user|pass|password|pwd)\\s*=\\s*['\"][^'\"]+['\"]– Hardcoded credentials detected. Store credentials securely outside of code.- Pattern 4: Credentials in code
- pattern
drupal_get_token\\(|form_token|\\$form\\[['\"]#token['\"]\\]\\s*=|drupal_valid_token\\(– Ensure proper CSRF protection is implemented for all authenticated actions.- Pattern 5: Missing or weak CSRF protection
- pattern
setcookie\\(|session_regenerate_id\\(false\\)|session_regenerate_id\\([^\\)]*– Use Drupal's session management. If custom code is required, ensure secure session handling practices.- Pattern 6: Insecure session management
- pattern
user\\.flood\\.yml|flood_control|UserFloodControl|user_failed_login_– Ensure proper account lockout and flood control mechanisms are configured to prevent brute force attacks.- Pattern 7: Missing account lockout protection
- pattern
user_pass_reset|password_reset|reset.*token– Verify password reset functionality uses secure tokens with proper expiration and validation.- Pattern 8: Insecure password reset implementation
- pattern
tfa|two_factor|multi_factor|2fa– Consider implementing multi-factor authentication for sensitive operations or user roles.- Pattern 9: Lack of multi-factor authentication
- pattern
\\$user->name\\s*=\\s*['\"]admin['\"]|\\$name\\s*=\\s*['\"]admin['\"]|->values\\(['\"](mdc:name|mail)['\"]\\)\\s*->\\s*set\\(['\"][^\\'\"]+['\"]\\)– Avoid creating default administrator accounts or test users in production code.- Pattern 10: Default or test accounts
- 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 · 103 lines · 1,406 tokens per session scan A d49487b8c931
drupal-authentication-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,406 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.