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 instructions/levifig/rails-instructions/rails-testinggit clone --depth 1 https://github.com/levifig/rails-instructionsWrote 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/instructions/levifig/rails-instructions/rails-testing)<a href="https://agentmods.dev/instructions/levifig/rails-instructions/rails-testing"><img src="https://agentmods.dev/badge/instructions/levifig/rails-instructions/rails-testing.svg" alt="Measured on agentmods" 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 | $0.01029 | $0.01029 |
| Opus 5 | $0.00515 | $0.00515 |
| Sonnet 5 | $0.00206 | $0.00206 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
rails-instructions rails-testing.instructions.md 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 4d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Testing Guide
Core Philosophy
- Test-Driven Development (TDD) as default practice
- Use Minitest and fixtures, not RSpec or factories
- Test behavior, not implementation details
- Keep tests fast, focused, and reliable
- Write tests that serve as documentation
Testing Principles
- Write tests first, then implementation
- One assertion per test when possible
- Test the happy path and edge cases
- Keep test data realistic and minimal
- Make tests independent and repeatable
Test Organization
- Mirror app structure in test directory
- Group related tests in the same file
- Use descriptive test names
- Keep test files focused and manageable
- Organize tests by feature or behavior
Fixtures Best Practices
- Use fixtures for test data, not factories
- Keep fixtures simple and realistic
- Reference fixtures by meaningful names
- Share fixtures across related tests
- Update fixtures when models change
Model Testing
- Test all validations thoroughly
- Verify associations work correctly
- Test scopes with various data sets
- Check business logic and calculations
- Ensure callbacks behave properly
Controller Testing
- Focus on HTTP concerns only
- Test authentication and authorization
- Verify response formats and status codes
- Check parameter filtering
- Test error handling scenarios
System Testing
- Test complete user workflows
- Use Capybara for browser automation
- Test JavaScript interactions
- Verify Turbo Frame updates
- Check responsive behavior
Service Object Testing
- Test services in complete isolation
- Mock external dependencies
- Verify success and failure paths
- Test edge cases and error conditions
- Ensure proper transaction handling
Integration Testing
- Test API endpoints thoroughly
- Verify request/response cycles
- Test authentication flows
- Check cross-controller workflows
- Validate data consistency
Test Data Management
- Keep test data minimal and focused
- Use fixtures for common scenarios
- Create data in tests for specific cases
- Clean up after tests when needed
- Avoid test data dependencies
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.
- 4d ago First seen · 209 lines · 1,029 tokens per session scan A da6a82be99be
rails-instructions rails-testing.instructions.md is an instructions file published in the GitHub repository levifig/rails-instructions (54 stars, last pushed 1y ago), licensed MIT. It adds 1,029 tokens to every session, about $0.0051 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 instructions, from other repositories
apex-accelerator javascript.instructions.md
JavaScript and Node.js conventions for validation scripts and tooling.
apex-accelerator python.instructions.md
Python coding conventions for diagram generation, MCP servers, and tooling scripts.
rails-agent-skills AGENTS.md
Instructions for igmarin/rails-agent-skills, covering rails agent skills, tests gate implementation, daily loop, when to load a skill and rails skills.
llm-ide-rules python-app.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering python app, factories and database & orm.
llm-ide-rules pytest-tests.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering pytest tests, example test and file structure.
llm-ide-rules python.instructions.md
Instructions for iloveitaly/llm-ide-rules, covering python, package management, typing, data manipulation and date & datetime.