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 skills/sergei-aronsen/claude-code-toolkit/railsnpx skills add sergei-aronsen/claude-code-toolkit --skill railsgit clone --depth 1 https://github.com/sergei-aronsen/claude-code-toolkitWrote 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/sergei-aronsen/claude-code-toolkit/rails)<a href="https://agentmods.dev/skills/sergei-aronsen/claude-code-toolkit/rails"><img src="https://agentmods.dev/badge/skills/sergei-aronsen/claude-code-toolkit/rails.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.1 | $0.00020 | $0.02883 |
| Opus 5 | $0.00010 | $0.01442 |
| Sonnet 5 | $0.00004 | $0.00577 |
| Haiku 4.5 | $0.00002 | $0.00288 |
Grade A, and why
Rails Expert 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 5d 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 — 539 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Expert Skill
This skill provides deep Rails expertise including ActiveRecord optimization, architectural patterns, security best practices, Hotwire integration, and testing strategies.
🔥 Common Pitfalls
N+1 Query Problem
# ❌ N+1 — 1 + N queries
Post.all.each do |post|
puts post.author.name
end
# ✅ Eager loading — 2 queries
Post.includes(:author).each do |post|
puts post.author.name
end
# ✅ Nested eager loading
Post.includes(author: :profile, comments: :user).all
# ✅ Preload vs Includes vs Eager_load
Post.preload(:author) # Separate query
Post.includes(:author) # Smart (preload or eager_load)
Post.eager_load(:author) # LEFT OUTER JOIN
Mass Assignment
# ❌ Dangerous - permits everything
params.permit!
# ❌ Sensitive fields
params.require(:user).permit(:name, :email, :admin)
# ✅ Safe - explicit whitelist
params.require(:user).permit(:name, :email, :bio)
# ✅ Admin fields with explicit check
if current_user.admin?
params.require(:user).permit(:name, :email, :admin)
else
params.require(:user).permit(:name, :email)
end
Callbacks Gotchas
# ❌ Side effects in callbacks
class User < ApplicationRecord
after_create :send_welcome_email # Hard to test, implicit
end
# ✅ Explicit in controller/service
class UsersController < ApplicationController
def create
@user = User.create!(user_params)
UserMailer.welcome(@user).deliver_later
end
end
# When callbacks ARE appropriate:
# - Data normalization (before_validation)
# - Timestamps
# - Counter cache updates
🏗️ Architecture Patterns
Service Objects (POROs)
# app/services/users/create_user.rb
module Users
class CreateUser
def initialize(params, current_user: nil)
@params = params
@current_user = current_user
end
def call
user = User.new(@params)
ActiveRecord::Base.transaction do
user.save!
create_profile(user)
enqueue_welcome_email(user)
end
Result.new(success: true, user: user)
rescue ActiveRecord::RecordInvalid => e
Result.new(success: false, errors: e.record.errors)
end
private
def create_profile(user)
Profile.create!(user: user)
end
def enqueue_welcome_email(user)
UserMailer.welcome(user).deliver_later
end
end
end
# Usage
result = Users::CreateUser.new(user_params).call
if result.success?
redirect_to result.user
else
render :new, status: :unprocessable_entity
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.
- 5d ago First seen · 539 lines · 20 tokens per session scan A c5a733287b23
Rails Expert is a skill published in the GitHub repository sergei-aronsen/claude-code-toolkit (5 stars, last pushed 19d ago), licensed MIT. It adds 20 tokens to every session and 2,883 once invoked, about $0.0001 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-31.
Other skills, from other repositories
contributing
Contribute to RubyLLM - set up the repo, run and record specs, add providers or chat options, work on the Rails integration, and edit docs. Use when fixing a bug, building a feature, writing specs, or changing documentation in the RubyLLM codebase.
new
Create a new project to start development quickly.
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…
ruby-patterns
Ruby/Rails: blocks, metaprogramming, ActiveRecord, Sidekiq, RSpec, Sorbet, Hanami. Triggers: Ruby, Rails, ActiveRecord, Sidekiq, RSpec, Gemfile, bundler, Hanami, Sorbet.
ruby-idioms
Ruby rewards expressiveness, convention, and developer happiness. Modern Ruby (3.x) favors pattern matching, Ractor for concurrency, and strict typing via Sorbet/RBS. Idiomatic Ruby = readable, tested, convention-following.
ruby-rules
Ruby coding rules: style, patterns, security, testing. Triggers: .rb, Gemfile, .gemspec, Rails, ActiveRecord, Sidekiq, RSpec, Sorbet, rubocop.