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/wintermeyer/cursor-rails-rules/readmegit clone --depth 1 https://github.com/wintermeyer/cursor-rails-rulesWhat 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.00007 | $0.00255 |
| Opus 5 | $0.00003 | $0.00128 |
| Sonnet 5 | $0.00001 | $0.00051 |
| Haiku 4.5 | $0.00001 | $0.00026 |
Grade A, and why
readme 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.
What it actually says
You are a senior programmer. Your role is to work with me as a pair programming team. Take care of the following things in case I forget them:
- When possible we always create at least one happy path test to check the functionality we just implimented or fixed. So if I e.g. create a new page we have to write a basic test that checks that that page answers with a 200 HTTP code.
- Always use
i18n.mdcsince this is a multilanguage project. - Use Tailwind CSS and avoid plain CSS.
Modify or create the code as requested. After completing the changes, execute the following commands in the terminal:
- Run tests to ensure everything still works:
bin/rails test:all - Automatically fix and check Ruby style issues:
bundle exec rubocop --format github --autocorrect-all - If any tests fail:
- Analyze the errors and attempt to fix them. It doesn't matter if it is old or new code.
- Modify the necessary code to resolve the failures.
- Re-run bin/rails test:all to confirm the fix.
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 · 25 lines · 7 tokens per session scan A 4b7a1d5e044b
readme is a cursor rule published in the GitHub repository wintermeyer/cursor-rails-rules (37 stars, last pushed 1y ago), licensed MIT. It adds 7 tokens to every session and 255 once invoked, about $0.0000 per session on Opus 5. 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
internationalization
Cursor rule "internationalization" from dtyq/magic, covering internationalization (i18n) rules, 国际化基本规范, 1. 文件结构, 2. 命名空间规范 and 3. 组件中使用国际化.
07-datagen
IF 生成物品/方块模型 JSON → 手动编写 JSON 在 src/main/resources/assets/{modid}/models/.
test-plan
Plan Katalon True Platform/TestOps testing for a release, sprint, or feature. Use when you need to translate quality goals into scope, prioritize testing by requirement coverage and risk, decide what to test first, or build the executable plan structure (folders, suites, and sprint/release association) that stands in…
wings
Authoring apps with the WINGS framework (Go compiled to WASM web components).
project-status
PriceGrab shipped state and product backlog (read first).
architecture
Architectural and cross-package changes — dependency direction, editor/runtime boundaries, scene schema, persistence, renderer packages. Use when changing package boundaries, serialized formats, or multiple layers. Do not apply to localized UI, styling, or test-only edits.