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 sorah/config --skill railsgit clone --depth 1 https://github.com/sorah/configWrote 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/sorah/config/rails)<a href="https://agentmods.dev/skills/sorah/config/rails"><img src="https://agentmods.dev/badge/skills/sorah/config/rails/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/sorah/config/rails"><img src="https://agentmods.dev/badge/skills/sorah/config/rails.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.00070 | $0.00964 |
| Opus 5.5 | $0.00028 | $0.00386 |
| Sonnet 5.5 | $0.00014 | $0.00193 |
| Haiku 4.5 | $0.00007 | $0.00096 |
Grade A, and why
rails 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 yesterday.
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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Conventions
Coding conventions and best practices for Ruby on Rails projects. Project-specific conventions (CLAUDE.md, style guides) always take priority over this guidance.
Related skills:
- API error responses (RFC 9457 problem details with the
problemgem): /sorah-guides:rails-problem - Protobuf-native APIs (Connect RPC with connect_rpc_rails, protobufable, protovalidate): /sorah-guides:rails-protobuf
- Sorbet typing: /sorah-guides:sorbet
Data Model — ActiveRecord
- Migrations: Specify column types, defaults, null constraints, and index definitions explicitly
- Index correctness: Unique vs non-unique; composite index column order matching query patterns
- Validations: Decide which layer enforces what — model-level validations vs database constraints
- Associations:
has_many,belongs_to,has_one— specify dependent behavior and foreign key constraints
Architecture & Design
- Concerns: Extract shared behaviors as ActiveRecord or ActionController concerns
- Where logic lives: Model callbacks vs service objects vs controller-level orchestration — prefer service objects for complex business logic
- Controller design: Keep actions thin; use before_action filters and strong parameters (or a declared protobuf message, see /sorah-guides:rails-protobuf)
- Errors: Raise error classes that render as problem details; no per-class
rescue_from(see /sorah-guides:rails-problem)
Configuration
- Namespaced settings: Use
Rails.configuration.x.namespace.keywith second-level namespacing; avoid single-levelRails.configuration.x.foo - Centralize ENV access: Define configuration in
config/environments/*.rbusingENV.fetch; avoid directENVaccess in application code - Avoid
Rails.envchecks: Do not useRails.env.production?or similar in application code; express environment differences through configuration values instead
# Good — config/environments/production.rb
Rails.configuration.x.oauth.client_id = ENV.fetch("OAUTH_CLIENT_ID")
Rails.configuration.x.session.idle_timeout = 30.minutes
# Good — application code
client_id = Rails.configuration.x.oauth.client_id
# Bad — direct ENV access in application code
client_id = ENV.fetch("OAUTH_CLIENT_ID")
# Bad — Rails.env check in application code
if Rails.env.production?
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.
- yesterday First seen · 82 lines · 70 tokens per session scan A 91eb5e1bebc1
rails is a skill published in the GitHub repository sorah/config (31 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 964 once invoked, about $0.0003 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-10-17.
Other skills, from other repositories
rails-expert
Rails 7+ specialist that optimizes Active Record queries with includes/eagerload, implements Turbo Frames and Turbo Streams for partial page updates, configures Action Cable for WebSocket connections, sets up Sidekiq workers for background job processing, and writes comprehensive RSpec test suites. Use when building…
new
Create a new project to start development quickly.
rails-conventions
Rootstrap Rails conventions. Use when writing, reviewing, or editing any Rails code — controllers, models, migrations, routes, views, mailers, initializers, locale files, or Rails config. Covers routing, ActiveRecord, migrations, i18n, time zones, mailers, assets, Bundler groups, and logging.
rails-idioms
Ruby on Rails framework patterns: ActiveRecord scopes, N+1 query prevention, model validations, RESTful routing, and RSpec/Minitest testing. Use when building, maintaining, or auditing Rails web applications and APIs. Pair with ruby-idioms.
ruby-rails
Conventions and best practices for building web applications with Ruby on Rails. Use when scaffolding Rails apps or generators, designing ActiveRecord models and migrations, wiring up Hotwire/Turbo/Stimulus interactivity, setting up background jobs or caching, or writing RSpec/Minitest coverage for Rails code.
rails-dev
Opinionated Rails conventions: rich models, concerns, CRUD-everything, state-as-records, minimal dependencies, Minitest with fixtures. Load this skill BEFORE any code-level thinking, not only before editing a file. It is required the moment a task touches Rails code in ANY way: designing or even just discussing a data…