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-vulnerable-componentsgit 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.01504 |
| Opus 5 | $0.00000 | $0.00752 |
| Sonnet 5 | $0.00000 | $0.00301 |
| Haiku 4.5 | $0.00000 | $0.00150 |
Grade A, and why
drupal-vulnerable-components 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drupal Vulnerable and Outdated Components Standards (OWASP A06:2021)
This rule enforces security best practices to prevent vulnerabilities related to outdated or vulnerable components in Drupal applications, as defined in OWASP Top 10:2021-A06.
Rule Details
-
Name: drupal_vulnerable_components
-
Description: Detect and prevent vulnerabilities related to outdated or vulnerable components in Drupal as defined in OWASP Top 10:2021-A06
Filters
- file extension pattern:
\\.(php|inc|module|install|info\\.yml|json)$ - file path pattern:
.*
Enforcement Checks
- Conditions:
- pattern
core:\\s*('|\")8\\.[0-6](mdc:'|\")|core_version_requirement:\\s*('|\")[^9].+('|\")– Potentially outdated Drupal core version detected. Consider upgrading to the latest secure version of Drupal 9 or 10.- Pattern 1: Outdated Drupal core version declaration
- pattern
drupal_set_message\\(|format_date\\(|drupal_render\\(|entity_load\\(|variable_get\\(|variable_set\\(– Deprecated function detected. Use modern replacements to ensure compatibility and security updates.- Pattern 2: Usage of deprecated functions
- pattern
jquery\\.min\\.js\\?v=1\\.|jquery-1\\.|jquery-2\\.|ckeditor/|tinymce/|angular\\.js@1\\.– Potentially vulnerable JavaScript library version detected. Update to the latest secure version.- Pattern 3: Known vulnerable libraries referenced
- pattern
<script\\s+src=['\"]http|<script\\s+src=['\"]//|<link\\s+[^>]*href=['\"]http– External scripts or stylesheets without Subresource Integrity (SRI) checks detected. Add integrity and crossorigin attributes.- Pattern 4: Direct inclusion of external scripts without SRI
- pattern
module:\\s*('[^']*captcha'|'recaptcha'|'xmlrpc'|'openid'|'php')– Potentially vulnerable or deprecated module detected. Consider using more secure alternatives.- Pattern 5: Use of obsolete or removed modules
- pattern
\"drupal/[^\"]+\":\\s*\"(~|\\^)?[0-9]\\.[0-9]\\.[0-9]\"– Hard-coded specific version detected in composer.json. Consider using version ranges to receive security updates.- Pattern 6: Hard-coded versions in composer.json
- pattern
mysql_|split\\(|ereg\\(|eregi\\(|create_function\\(|each\\(– Deprecated or insecure PHP function detected. Use modern alternatives for better security.- Pattern 7: Outdated or insecure PHP API usage
- pattern
type:\\s*module\\s*\\nname:– Ensure your module specifies core_version_requirement to prevent installation on unsupported Drupal versions.- Pattern 8: Usage of contrib modules without version constraints
- pattern
composer\\.json– Consider adding drupal/core-security-advisories as a dev dependency to detect known vulnerable packages.- Pattern 9: Missing security advisories handling in composer.json
- pattern
check_plain\\(|filter_xss\\(|filter_xss_admin\\(– Legacy text sanitization function detected. Use Html::escape() or Xss::filter() instead.- Pattern 10: Direct usage of vulnerable sanitization functions
- 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,504 tokens per session scan A 9eac9a098f71
drupal-vulnerable-components 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,504 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.