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 jorgegorka/ariadna --skill rails-testinggit clone --depth 1 https://github.com/jorgegorka/ariadnaWrote 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/jorgegorka/ariadna/rails-testing)<a href="https://agentmods.dev/skills/jorgegorka/ariadna/rails-testing"><img src="https://agentmods.dev/badge/skills/jorgegorka/ariadna/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/jorgegorka/ariadna/rails-testing"><img src="https://agentmods.dev/badge/skills/jorgegorka/ariadna/rails-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.00034 | $0.00935 |
| Opus 5 | $0.00017 | $0.00467 |
| Sonnet 5 | $0.00007 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00093 |
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 9d 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Testing Skill
Testing strategy for Rails applications using Minitest and fixtures. Not RSpec, not FactoryBot.
Sub-files:
- FIXTURES.md — Fixture patterns and test data management
- SYSTEM-TESTS.md — System and integration test conventions
Philosophy
- Test at the model level first — Business logic lives in models; that's where tests provide the most value
- Fixtures over factories — YAML fixtures are deterministic, fast, and require no setup code
- Always set
Current.session— Lambda defaults and multi-tenancy depend on it; forgetting it is the #1 test failure - Test behavior, not implementation — Assert on outcomes, not internal method calls
- Use
assert_differencefor state changes — Catches false positives that boolean checks alone miss
File Organization
test/
models/
card/
archivable_test.rb # Concern tests get their own file
card_test.rb
controllers/
cards/
closures_controller_test.rb
jobs/
notify_recipients_job_test.rb
fixtures/
cards.yml
sessions.yml
Standard Test Structure
require "test_helper"
class Card::CloseableTest < ActiveSupport::TestCase
setup do
Current.session = sessions(:david) # Always — sets user + account context
end
test "close creates closure record and marks card closed" do
card = cards(:logo)
assert_difference -> { Closure.count }, +1 do
card.close
end
assert card.closed?
end
end
Model Testing
State Changes
Nest assert_difference blocks when multiple record types change together:
assert_difference -> { Closure.count }, +1 do
assert_difference -> { Event.count }, +1 do
card.close
end
end
assert card.closed?
assert_equal "card_closed", Event.last.action
Event Attributes
Count alone is insufficient — always verify attributes:
event = Event.last
assert_equal "card_archived", event.action
assert_equal card, event.eventable
assert_equal Current.user, event.creator
# For events with particulars:
assert_equal old_board.name, event.particulars["old_board"]
What ships with it
2 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.
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.
- 9d ago First seen · 161 lines · 34 tokens per session scan A 638d42ebfa91
rails-testing is a skill published in the GitHub repository jorgegorka/ariadna (21 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 935 once invoked, about $0.0002 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 skills, from other repositories
neuron-test-engineer
Write tests for Neuron AI agents, RAG systems, workflows, and tools using the built-in testing utilities. Use this skill when the user mentions testing agents, writing unit tests, mocking AI providers, testing tool execution, verifying RAG retrieval, testing workflow behavior, or creating test cases for Neuron AI…
nw-test-organization-conventions
Test directory structure patterns by architecture style, language conventions, naming rules, and fixture placement. Decision tree for selecting test organization strategy.
test-automation
Execute Vitest and Playwright test suites with result collection and failure analysis.
qa-testing-strategy
Risk-based test strategy for software delivery. Use when defining coverage, setting CI gates, managing flaky tests, choosing test layers, or establishing release criteria.
testing-strategies
Systematic testing for confidence without over-testing — the right test at the right level.
converter-qa
Test harness for validating converter outputs with 284 assertions across all converter muscles.