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/javascript-standardsgit 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.00362 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
javascript-standards 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:
- javascript-standards — 100% identical, 0 lines differ
What it actually says
JavaScript Development Standards
actions:
-
type: enforce conditions:
-
pattern: "\(function\s*\(\$\)\s*\{[^}]\}\)\s\(jQuery\)" message: "Use Drupal behaviors instead of IIFE"
-
pattern: "\$\('[^']*'\)" message: "Cache jQuery selectors for better performance"
-
pattern: "\.ajax\(\{[^}]*success:" message: "Implement proper error handling for AJAX calls"
-
pattern: "var\s+" message: "Use const or let instead of var (ES6+)"
-
-
type: suggest message: | JavaScript Best Practices:
- Use Drupal behaviors for all JavaScript
- Implement proper error handling for AJAX
- Cache jQuery selectors
- Use ES6+ features
- Add proper documentation
- Follow Drupal JavaScript coding standards
- Use proper event delegation
- Implement proper error handling
- Use async/await for asynchronous operations
- Follow proper module pattern
-
type: validate conditions:
-
pattern: "Drupal\.behaviors\.\w+" message: "Implement JavaScript functionality using Drupal behaviors"
-
pattern: "/\\[^]\*/" message: "Add JSDoc documentation for JavaScript functions"
-
metadata: priority: high version: 1.0
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 · 52 lines · 362 tokens per session scan A e452570f7020
javascript-standards 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 362 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.