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 ombulabs/claude-code_rails-upgrade-skill --skill upgrade-cleanupgit clone --depth 1 https://github.com/ombulabs/claude-code_rails-upgrade-skillWrote 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/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup)<a href="https://agentmods.dev/skills/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup"><img src="https://agentmods.dev/badge/skills/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup/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/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup"><img src="https://agentmods.dev/badge/skills/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup.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.00139 | $0.00776 |
| Opus 5 | $0.00069 | $0.00388 |
| Sonnet 5 | $0.00028 | $0.00155 |
| Haiku 4.5 | $0.00014 | $0.00078 |
Grade A, and why
upgrade-cleanup 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Upgrade Cleanup Skill
Companion to the rails-upgrade plugin. Runs the cleanup pass that removes dual-boot scaffolding and aligns the codebase to the new version baseline.
When activated, follow the workflow in workflows/upgrade-cleanup-workflow.md end-to-end. Before any destructive step, confirm direction with the user (Phase 0 Step 1): are they keeping the next version (finishing the upgrade) or keeping the current version (abandoning or pausing this hop)? Every subsequent step branches on that answer. To detect the next version, read the Gemfile (look for the if NextRails.next? / else block; the next? branch holds the upgraded-to version) or Gemfile.next.lock. Do NOT rely on Gemfile.lock alone, since during dual-boot it still pins the current version.
When to Run
Run when the user has explicitly decided to end the dual-boot phase in one of two directions:
- Keep next: upgrade is done (final hop or stopping point), drop the
else/ current branches. - Keep current: abandoning or pausing this hop, drop the
if NextRails.next?/ next branches andGemfile.next*.
Either way the previous parallel branch must no longer be needed (no rollback window). Deployment to production is not a hard prerequisite.
Ownership and Delegations
This skill owns the cleanup. Phase 1 below is the step list to follow. The dual-boot skill's workflows/cleanup-workflow.md is older optional reading; if it drifts from this workflow, this workflow wins.
- Dual-boot scaffolding removal: performed here in Phase 1.
load_defaultsalignment: out of scope. Therails-upgradeskill handles this via itsrails-load-defaultsstep before cleanup runs.
Critical Rules
- Do NOT leave
NextRails.next?orNextRails.current?branches in the tree. That is the failure mode this skill exists to prevent. - Do NOT start removing branches before confirming direction. Keeping the wrong side throws away the work the user wants to keep. If the user has not stated next vs current, ask.
What ships with it
1 file 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.
- 10d ago First seen · 42 lines · 139 tokens per session scan A eab46b861c79
upgrade-cleanup is a skill published in the GitHub repository ombulabs/claude-code_rails-upgrade-skill (382 stars, last pushed 12d ago), licensed MIT. It adds 139 tokens to every session and 776 once invoked, about $0.0007 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
test-driven-development
Strict red-green-refactor TDD workflow for implementing features, fixing bugs, or changing behavior in Rails applications. Enforces the discipline of writing a failing test before any production code. Use whenever you want to implement with TDD — whether a new feature, a bugfix, a refactor, or any behavior change.
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.
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-conventions
Rootstrap Ruby style conventions. Use when writing, reviewing, or editing any Ruby source file (.rb, .rake, Gemfile, Rakefile, .gemspec, config.ru) to ensure code follows the Rootstrap Ruby style guide — covers layout, syntax, naming, classes/modules, exceptions, collections, strings, regexes, metaprogramming, and…
rails-audit-thoughtbot
Perform comprehensive code audits of Ruby on Rails applications based on thoughtbot best practices. Use this skill when the user requests a code audit, code review, quality assessment, or analysis of a Rails application. The skill analyzes the entire codebase focusing on testing practices (RSpec), security…
rails-load-defaults
Incrementally upgrade Rails config.loaddefaults by walking through each newframeworkdefaults config one at a time. Use this skill whenever the user mentions loaddefaults upgrade, newframeworkdefaults, framework defaults, or wants to bring their Rails app's default configuration up to match their Rails version. Also…