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/1006-testing)<a href="https://agentmods.dev/rules/andyw8/rails_rules/1006-testing"><img src="https://agentmods.dev/badge/rules/andyw8/rails_rules/1006-testing/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/1006-testing"><img src="https://agentmods.dev/badge/rules/andyw8/rails_rules/1006-testing.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.00524 |
| Opus 5.5 | $0.00000 | $0.00210 |
| Sonnet 5.5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
1006-testing 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.
What it actually says
Testing Standards
Context
- In Ruby on Rails 8.0 test files
- Using Minitest for testing
- Tests should be thorough and maintainable
Requirements
- Use Minitest for all tests
- Write tests for models, controllers, services, and other components
- Use fixtures for test data
- Organize tests into appropriate test classes
- Use descriptive test names with test_ prefix (e.g., test_valid_user_can_login)
- Use assertions that best match what you're testing
- Keep tests focused on a single concern
- Use setup/teardown methods for common setup code
- Use test helpers for reusable test code
- Test both happy and sad paths
- Test edge cases and boundary conditions
- Avoid testing the framework itself
- Keep tests independent and idempotent
- Don't pipe test output into cat (
bin/rails testnotbin/rails test | cat)
Examples
class UserTest < ActiveSupport::TestCase setup do @user = users(:one) @account = accounts(:one) end
test "valid user" do assert @user.valid? end
test "invalid without email" do @user.email = nil refute @user.valid? assert_not_nil @user.errors[:email] end
test "can be assigned to account" do account_user = AccountUser.new(user: @user, account: @account) assert account_user.valid? end
test "can have admin role" do account_user = AccountUser.new(user: @user, account: @account, admin: true) assert account_user.admin? assert_includes account_user.active_roles, :admin end end
</example>
<example type="invalid">
```ruby
require "test_helper"
class UserTest < ActiveSupport::TestCase
def setup
@user = User.new(name: "Test User", email: "[email protected]")
end
def test_it_works
@user.save
assert_equal 1, User.count
User.all.each do |u|
assert u.valid?
end
@user.update(email: nil)
assert_equal false, @user.valid?
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.
- 1mo ago First seen · 89 lines · 0 tokens per session scan A 7bca0438ac8e
1006-testing 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 524 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
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
common-fixes
Utility for VAN QA common validation fixes.