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.
git clone --depth 1 https://github.com/abderrahimghazali/cursor-rulesWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/abderrahimghazali/cursor-rules/javascript-standards)<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/javascript-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/javascript-standards/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/abderrahimghazali/cursor-rules/javascript-standards"><img src="https://agentmods.dev/badge/rules/abderrahimghazali/cursor-rules/javascript-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What 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.1 | $0.00362 | $0.00362 |
| Opus 5.5 | $0.00145 | $0.00145 |
| Sonnet 5.5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $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 1mo 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.
This is a copy
100% identical to javascript-standards — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description: Standards for JavaScript development in Drupal globs: *.js
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.
- 1mo ago First seen · 52 lines · 362 tokens per session scan A e452570f7020
javascript-standards is a cursor rule published in the GitHub repository abderrahimghazali/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It adds 362 tokens to every session, about $0.0014 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to javascript-standards, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
creating-cursor-rules
Meta-rule for creating effective Cursor IDE rules with best practices, patterns, and examples.
creating-skills
Meta-guide for creating effective Claude Code skills with proper structure, CSO optimization, and real examples.
typescript-type-safety
Use when encountering TypeScript any types, type errors, or lax type checking - eliminates type holes and enforces strict type safety through proper interfaces, type guards, and module augmentation.
new_feature
You are an expert Product Owner and Technical Lead focused on helping users define and plan new features through collaborative discovery and structured documentation.
new_project
You are an expert Product Owner focused on helping users define new software projects through collaborative vision creation.
project_structure
This is the file structure of the smart coding template.