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 zarpay/rails-template --skill rails-upgradegit clone --depth 1 https://github.com/zarpay/rails-templateWrote 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/zarpay/rails-template/rails-upgrade)<a href="https://agentmods.dev/skills/zarpay/rails-template/rails-upgrade"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/rails-upgrade/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/zarpay/rails-template/rails-upgrade"><img src="https://agentmods.dev/badge/skills/zarpay/rails-template/rails-upgrade.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.00059 | $0.02240 |
| Opus 5 | $0.00030 | $0.01120 |
| Sonnet 5 | $0.00012 | $0.00448 |
| Haiku 4.5 | $0.00006 | $0.00224 |
Grade A, and why
rails-upgrade 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 10d 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 — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rails Upgrade
Overview
This skill provides a systematic workflow for upgrading Rails applications, covering versions 5.2 through the latest release. It fetches live configuration diffs from railsdiff.org via the GitHub API, performs direct codebase detection using Grep, Glob, and Read tools, and compiles structured upgrade reports — all without requiring external skill dependencies.
Announce at start: "I'm using the rails-upgrade skill to guide this upgrade."
Ruby Version Compatibility
| Rails | Minimum Ruby | Recommended Ruby |
|---|---|---|
| 5.2 | 2.2.2 | 2.5+ |
| 6.0–6.1 | 2.5.0 | 2.7+ |
| 7.0–7.1 | 2.7.0 | 3.1+ |
| 7.2 | 3.1.0 | 3.3+ |
| 8.0+ | 3.2.0 | 3.3+ |
The Workflow
Step 0: Version Assessment
- Read
GemfileandGemfile.lockto find the current Rails gem version - Read
config/application.rbto find the currentconfig.load_defaultsvalue - Check
.ruby-versionorGemfilefor the Ruby version — verify against the compatibility table above - Confirm the target version with the user if not specified
- If the jump spans more than one minor version, plan sequential hops (e.g., 7.0 → 8.0 requires 7.0 → 7.1 → 7.2 → 8.0)
- Output: version assessment summary (current Rails, current Ruby, target Rails, required Ruby, upgrade path)
Step 1: Test Suite Verification
HARD GATE: Run the test suite before ANY upgrade work.
If tests fail: STOP. Report failures. Do NOT proceed until baseline is green.
A failing baseline makes post-upgrade failures ambiguous.
- Detect framework: check for
spec/(RSpec) ortest/(Minitest) - Run:
bundle exec rspecorbundle exec rails test - Record: total tests, passing, failing, pending
- If any failures: STOP, report them, offer to help fix
- If all pass: record as baseline, proceed to Step 2
Step 2: Configuration Diff (railsdiff.org)
What ships with it
8 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.
- references/breaking-changes.md 47 KB
- references/deprecation-timeline.md 5.6 KB
- references/detection-patterns.md 17 KB
- references/dual-boot-guide.md 2.8 KB
- references/gem-compatibility.md 7.1 KB
- references/load-defaults-guide.md 5.2 KB
- references/troubleshooting.md 4.9 KB
- scripts/fetch-changelogs.sh 8.1 KB runs code
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.
- 10d ago First seen · 233 lines · 59 tokens per session scan A dee52175c236
rails-upgrade is a skill published in the GitHub repository zarpay/rails-template (9 stars, last pushed 28d ago), licensed MIT. It adds 59 tokens to every session and 2,240 once invoked, about $0.0003 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
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.
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.
ruby-expert
Expert-level Ruby development with Rails, modern features, testing, and best practices. Use when the user mentions Ruby on Rails, RSpec, gem, Sinatra, or metaprogramming, or when the task involves Ruby 3+ Features, Object-Oriented, Functional Features, or Pattern Matching.
draper-decorators
This skill should be used when the user asks to "create a decorator", "write a decorator", "move logic into decorator", "clean logic out of the view", "isn't it decorator logic", "test a decorator", or mentions Draper, keeping views clean, or representation logic in decorators. Should also be used when editing…