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/andyw8/rails_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/andyw8/rails_rules/1004-javascript-stimulus)<a href="https://agentmods.dev/rules/andyw8/rails_rules/1004-javascript-stimulus"><img src="https://agentmods.dev/badge/rules/andyw8/rails_rules/1004-javascript-stimulus/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/andyw8/rails_rules/1004-javascript-stimulus"><img src="https://agentmods.dev/badge/rules/andyw8/rails_rules/1004-javascript-stimulus.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.00000 | $0.00675 |
| Opus 5.5 | $0.00000 | $0.00270 |
| Sonnet 5.5 | $0.00000 | $0.00135 |
| Haiku 4.5 | $0.00000 | $0.00068 |
Grade A, and why
1004-javascript-stimulus 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
JavaScript and Stimulus Controller Standards
Context
- In Ruby on Rails 8.0 JavaScript
- Using Stimulus.js for interactive components
- Using ES6 features
- Using TailwindCSS Stimulus Components
Requirements
- Use ES6 syntax (arrow functions, destructuring, etc.)
- Add comments at the top of Stimulus controllers explaining their purpose and usage examples
- Follow Stimulus controller naming conventions
- Use data-controller, data-action, and data-[controller]-target attributes
- Define static targets, values, and classes at the top of controller classes
- Initialize connections in the connect() lifecycle method
- Clean up resources in the disconnect() lifecycle method
- Use the tailwindcss-stimulus-components library for common components:
- Alert, Dropdown, Modal, Tabs, Popover, Toggle, Slideover
- Keep controller actions focused on a single responsibility
- Use event delegation where appropriate
- Document values properties with their types and defaults
- Avoid DOM manipulation where possible, prefer toggling classes
Examples
import { Controller } from "@hotwired/stimulus" import { autoUpdate, autoPlacement, computePosition, offset, arrow } from "@floating-ui/dom"
export default class extends Controller { // Define expected properties and their types static values = { content: String, placement: String, offset: { type: Number, default: 6 }, allowHtml: { type: Boolean, default: true } }
// Initialize on connection connect() { this.createTooltipElements() this.cleanup = autoUpdate(this.element, this.tooltip, this.updatePosition.bind(this)) this.addEvents() }
// Clean up resources on disconnect disconnect() { this.removeEvents() this.tooltip?.remove() this.cleanup?.() }
// Creates DOM elements for the tooltip createTooltipElements() { this.tooltip = document.createElement("div") this.tooltip.className = "tooltip" this.tooltip.setAttribute("role", "tooltip")
this.tooltipContent = document.createElement("div")
this.tooltipContent.className = "tooltip-content"
this.tooltipArrow = document.createElement("div")
this.tooltipArrow.className = "tooltip-arrow"
this.tooltip.appendChild(this.tooltipContent)
this.tooltip.appendChild(this.tooltipArrow)
document.body.appendChild(this.tooltip)
this.updateContent()
}
// Updates tooltip content when content value changes contentValueChanged() { this.updateContent() } }
</example>
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 · 91 lines · 0 tokens per session scan A 1b3943840673
1004-javascript-stimulus is a cursor rule published in the GitHub repository andyw8/rails_rules (4 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 675 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-31.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).