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 skills add pproenca/dot-skills --skill rails-testinggit clone --depth 1 https://github.com/pproenca/dot-skillsWrote 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/skills/pproenca/dot-skills/rails-testing)<a href="https://agentmods.dev/skills/pproenca/dot-skills/rails-testing"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/rails-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/skills/pproenca/dot-skills/rails-testing"><img src="https://agentmods.dev/badge/skills/pproenca/dot-skills/rails-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00103 | $0.01882 |
| Opus 5.5 | $0.00041 | $0.00753 |
| Sonnet 5.5 | $0.00021 | $0.00376 |
| Haiku 4.5 | $0.00010 | $0.00188 |
Grade A, and why
rails-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 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Community Ruby on Rails Testing Best Practices
Comprehensive testing guide for Ruby on Rails applications, maintained by Community. Contains 46 rules across 8 categories, prioritized by impact to guide automated test generation, review, and refactoring.
When to Apply
Reference these guidelines when:
- Writing new RSpec specs for models, requests, system tests, or jobs
- Setting up FactoryBot factories with traits and sequences
- Writing Capybara system tests for user journeys
- Testing background jobs with Sidekiq or Active Job
- Reviewing test code for anti-patterns (mystery guests, flaky tests, slow specs)
- Optimizing test suite performance and CI pipeline speed
- Organizing test files, shared examples, and custom matchers
Rule Categories by Priority
| Priority | Category | Impact | Prefix |
|---|---|---|---|
| 1 | Test Design & Structure | CRITICAL | design- |
| 2 | Test Data Management | CRITICAL | data- |
| 3 | Model Testing | HIGH | model- |
| 4 | Request & Controller Testing | HIGH | request- |
| 5 | System & Acceptance Testing | MEDIUM-HIGH | system- |
| 6 | Async & Background Job Testing | MEDIUM | async- |
| 7 | Test Performance & Reliability | MEDIUM | perf- |
| 8 | Test Organization & Maintenance | LOW-MEDIUM | org- |
Quick Reference
1. Test Design & Structure (CRITICAL)
design-four-phase-test- Use four-phase test structure (setup, exercise, verify, teardown)design-behavior-over-implementation- Test observable behavior, not internal implementationdesign-one-assertion-per-test- One logical expectation per test for precise failure diagnosisdesign-descriptive-test-names- Write test names that read like specificationsdesign-avoid-mystery-guest- Make all test data visible within the test itselfdesign-avoid-conditional-logic- No if/else or loops in test codedesign-explicit-subject- Name subjects explicitly instead of using implicit subject
What ships with it
50 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- AGENTS.md 204 B
- assets/templates/_template.md 625 B
- metadata.json 1.3 KB
- references/_sections.md 2.3 KB
- references/async-separate-enqueue-from-perform.md 2.9 KB
- references/async-test-after-commit.md 2.9 KB
- references/async-test-job-perform.md 2.3 KB
- references/async-test-mailer-delivery.md 3.0 KB
- references/async-use-fake-mode-default.md 2.6 KB
- references/data-avoid-fixture-coupling.md 2.8 KB
- references/data-build-over-create.md 2.7 KB
- references/data-factory-traits.md 2.2 KB
- references/data-minimal-attributes.md 2.1 KB
- references/data-sequence-unique-values.md 2.2 KB
- references/data-transient-attributes.md 2.7 KB
- references/design-avoid-conditional-logic.md 2.3 KB
- references/design-avoid-mystery-guest.md 2.5 KB
- references/design-behavior-over-implementation.md 2.5 KB
- references/design-descriptive-test-names.md 2.3 KB
- references/design-explicit-subject.md 2.3 KB
- references/design-four-phase-test.md 2.6 KB
- references/design-one-assertion-per-test.md 2.7 KB
- references/model-avoid-testing-framework.md 2.9 KB
- references/model-test-associations.md 2.3 KB
- references/model-test-callbacks-sparingly.md 2.7 KB
- references/model-test-custom-methods.md 3.4 KB
- references/model-test-enums.md 3.4 KB
- references/model-test-scopes.md 2.7 KB
- references/model-test-validations.md 2.8 KB
- references/org-avoid-deep-nesting.md 3.2 KB
- references/org-custom-matchers.md 3.7 KB
- references/org-file-structure-mirrors-app.md 3.2 KB
- references/org-shared-examples-sparingly.md 3.6 KB
- references/perf-avoid-before-all-mutation.md 3.0 KB
- references/perf-database-strategy.md 2.1 KB
- references/perf-parallel-tests.md 2.1 KB
- references/perf-profile-slow-specs.md 3.2 KB
- references/perf-quarantine-flaky-tests.md 2.7 KB
- references/request-json-response-structure.md 4.0 KB
- references/request-over-controller-specs.md 2.3 KB
- references/request-test-authentication.md 2.9 KB
- references/request-test-authorization.md 3.6 KB
- references/request-test-params-validation.md 3.8 KB
- references/request-test-response-status.md 3.2 KB
- references/system-avoid-sleep.md 2.6 KB
- references/system-database-state.md 2.5 KB
- references/system-page-objects.md 2.6 KB
- references/system-screenshot-on-failure.md 2.6 KB
- references/system-test-critical-paths.md 3.1 KB
- references/system-use-accessible-selectors.md 2.1 KB
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 · 120 lines · 103 tokens per session scan A 72c4ee44e945
rails-testing is a skill published in the GitHub repository pproenca/dot-skills (221 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 1,882 once invoked, about $0.0004 per session on Opus 5.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 skills, from other repositories
rspec-conventions
Rootstrap RSpec conventions. Use when writing, reviewing, or editing RSpec test files (spec//spec.rb, spec/railshelper.rb, spec/spechelper.rb, spec/support//.rb) or factories. Covers describe/context structure, let/subject, matchers, factories, mocking/stubbing, shared examples, and spec types (model, request…
testunit-skill
Generates Test::Unit tests in Ruby. Classic xUnit-style testing with assert methods and test case classes. Use when user mentions "Test::Unit", "assertequal Ruby", "Ruby test-unit". Triggers on: "Test::Unit", "Ruby test-unit", "assertequal Ruby" (not RSpec).
rspec
RSpec testing best practices for Ruby and Rails applications, covering test organization, data management, and isolation patterns.
ruby
Ruby development guidelines covering idiomatic code style, Ruby 3.x features, testing with RSpec, and best practices for building maintainable Ruby applications.
test-service
Use when writing RSpec for a service object under spec/services/. Test the public .call contract. Trigger words: service spec, test service object, spec/services.
write-tests
Use when writing or cleaning up Rails RSpec. Run the spec and keep the real output. Trigger words: write spec, rspec, test-driven, write tests.