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/wintermeyer/cursor-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/wintermeyer/cursor-rails-rules/views)<a href="https://agentmods.dev/rules/wintermeyer/cursor-rails-rules/views"><img src="https://agentmods.dev/badge/rules/wintermeyer/cursor-rails-rules/views/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/wintermeyer/cursor-rails-rules/views"><img src="https://agentmods.dev/badge/rules/wintermeyer/cursor-rails-rules/views.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.01437 |
| Opus 5.5 | $0.00000 | $0.00575 |
| Sonnet 5.5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00144 |
Grade A, and why
views 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 2mo 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 — 250 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure
- Directory Organization
app/views/
├── layouts/
├── shared/
├── components/
└── [resource]/
├── index.html.erb
├── show.html.erb
├── _form.html.erb
└── [action].html.erb
- Naming Conventions
- Use lowercase
- Use underscores for spaces
- Prefix partials with underscore
- Use meaningful names
- Follow resource naming
Templates
- Layout Files
<!DOCTYPE html>
<html>
<head>
<title><%= content_for?(:title) ? yield(:title) : 'Default Title' %></title>
<%= csrf_meta_tags %>
<%= csp_meta_tag %>
<%= stylesheet_link_tag "application" %>
<%= javascript_include_tag "application", defer: true %>
</head>
<body>
<%= render "shared/header" %>
<main>
<%= render "shared/flash" %>
<%= yield %>
</main>
<%= render "shared/footer" %>
</body>
</html>
- Index Views
<% content_for :title, t('.title') %>
<div class="container">
<header class="mb-4">
<h1><%= t('.title') %></h1>
<%= link_to t('.new'), new_resource_path, class: 'button' %>
</header>
<%= render 'filter_form' if @filters.present? %>
<% if @resources.any? %>
<%= render @resources %>
<% else %>
<%= render 'shared/empty_state' %>
<% end %>
<%= render 'shared/pagination', collection: @resources %>
</div>
- Show Views
<% content_for :title, t('.title', name: @resource.name) %>
<div class="container">
<header class="mb-4">
<h1><%= t('.title', name: @resource.name) %></h1>
<div class="actions">
<%= link_to t('.edit'), edit_resource_path(@resource), class: 'button' %>
<%= button_to t('.delete'), resource_path(@resource),
method: :delete,
class: 'button button--danger',
data: { confirm: t('.confirm_delete') } %>
</div>
</header>
<%= render 'details', resource: @resource %>
<%= render 'related_resources' if @resource.related.any? %>
</div>
- Form Partials
<%= form_with model: @resource, class: 'form' do |f| %>
<%= render 'shared/error_messages', resource: @resource %>
<div class="form-group">
<%= f.label :attribute %>
<%= f.text_field :attribute, class: 'form-control' %>
<%= f.error_message :attribute %>
</div>
<div class="actions">
<%= f.submit class: 'button' %>
<%= link_to t('.cancel'), :back, class: 'button button--secondary' %>
</div>
<% end %>
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.
- 2mo ago First seen · 250 lines · 0 tokens per session scan A f736e155b20c
views is a cursor rule published in the GitHub repository wintermeyer/cursor-rails-rules (37 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,437 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
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).