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/testing-factory_bot)<a href="https://agentmods.dev/rules/wintermeyer/cursor-rails-rules/testing-factory_bot"><img src="https://agentmods.dev/badge/rules/wintermeyer/cursor-rails-rules/testing-factory_bot/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/testing-factory_bot"><img src="https://agentmods.dev/badge/rules/wintermeyer/cursor-rails-rules/testing-factory_bot.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.01382 |
| Opus 5.5 | $0.00000 | $0.00553 |
| Sonnet 5.5 | $0.00000 | $0.00276 |
| Haiku 4.5 | $0.00000 | $0.00138 |
Grade A, and why
testing-factory_bot 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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
FactoryBot Standards
Use FactoryBot rather than fixtures in Rails tests.
Install the factory_bot gem if it is not already included in the Gemfile.
Factory Organization
- Directory Structure
test/factories/
├── users.rb
├── posts.rb
├── comments.rb
└── traits/
├── addressable.rb
└── timestampable.rb
- Basic Factory Structure
# test/factories/users.rb
FactoryBot.define do
factory :user do
first_name { Faker::Name.first_name }
last_name { Faker::Name.last_name }
email { Faker::Internet.email }
password { "password123" }
trait :admin do
role { "admin" }
admin_since { Time.current }
end
trait :inactive do
active { false }
deactivated_at { Time.current }
end
factory :admin_user do
role { "admin" }
admin_since { Time.current }
end
end
end
Best Practices
- Factory Design
- Keep factories minimal
- Use traits for variations
- Use sequences for unique values
- Follow database constraints
- Naming Conventions
- Use singular form for factory names
- Use descriptive trait names
- Prefix dynamic values with
with_ - Use verb past tense for states
- Data Generation
- Use Faker for realistic data
- Use sequences for unique fields
- Use associations when needed
- Keep data consistent
- Performance
- Avoid unnecessary associations
- Use
buildinstead ofcreatewhen possible - Use
traitsto minimize database hits - Clean up test data properly
Common Patterns
- Associations
# test/factories/posts.rb
FactoryBot.define do
factory :post do
association :user
title { Faker::Lorem.sentence }
content { Faker::Lorem.paragraphs(number: 3).join("\n\n") }
trait :with_comments do
after(:create) do |post|
create_list(:comment, 3, post: post)
end
end
trait :published do
published_at { Time.current }
status { "published" }
end
end
end
# test/factories/comments.rb
FactoryBot.define do
factory :comment do
association :user
association :post
content { Faker::Lorem.paragraph }
end
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 · 251 lines · 0 tokens per session scan A 3751ec4fa815
testing-factory_bot 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,382 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
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.