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.
/plugin marketplace add ombulabs/claude-code_rails-upgrade-skillnpx agentmods add plugins/ombulabs/claude-code_rails-upgrade-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/plugins/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup)<a href="https://agentmods.dev/plugins/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup"><img src="https://agentmods.dev/badge/plugins/ombulabs/claude-code_rails-upgrade-skill/upgrade-cleanup.svg" alt="Measured on agentmods" height="20"></a>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 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.
What it actually says
{
"name": "upgrade-cleanup",
"version": "0.1.0",
"description": "Clean up after a Rails upgrade. Drops NextRails.next? / NextRails.current? branches and retires dual-boot scaffolding (Gemfile.next, conditional Gemfile groups, dual-boot CI job).",
"skills": "./upgrade-cleanup/",
"author": {
"name": "OmbuLabs",
"url": "https://github.com/ombulabs"
},
"repository": "https://github.com/ombulabs/claude-code_rails-upgrade-skill",
"license": "MIT",
"keywords": [
"ruby",
"rails",
"upgrade",
"cleanup",
"next_rails",
"dual-boot",
"fastruby"
]
}
What it installs
The manifest is a name and a version. 1 skill travel with it, and installing the plugin installs all of them — 139 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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 · 22 lines scan A 2f636b91c851
upgrade-cleanup is a plugin published in the GitHub repository ombulabs/claude-code_rails-upgrade-skill (381 stars, last pushed 8d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
rails-consultant marketplace
Plugin marketplace listing 1 plugin: rails-consultant.
rails-consultant
A collection of skills for Rails development and consulting, with an emphasis on learning, communication, and client success.
swarm-skill
Multi-agent codebase audit skill for Claude Code — spawns parallel subagents (security, performance, tests, architecture, dead-code) and synthesizes their findings into a prioritized action plan.
crisp
A BA/PM framework for AI builders. Full product discovery — problem definition, stakeholder mapping, user journeys, tech stack, and sprint-ready AI specs — before you write a single line of code.
dev-pipeline
A 5-phase development pipeline (requirement engineering, system architecture, task generation, verified implementation, code review) with an optional QA gate (plan-qa + execute-qa) for changes that have a running surface worth driving — independent of /review, run sequentially or in parallel at the developer's…
lean-coach
A Lean business-development coach: guide a venture through Running Lean — Lean Canvas, riskiest-assumption testing, customer interviews, experiments, and product/market fit — and role-play the customers, investors, and advisors you test it with.