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.
git clone --depth 1 https://github.com/slbug/claude-ruby-grape-railsWrote 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/agents/slbug/claude-ruby-grape-rails/migration-safety-reviewer)<a href="https://agentmods.dev/agents/slbug/claude-ruby-grape-rails/migration-safety-reviewer"><img src="https://agentmods.dev/badge/agents/slbug/claude-ruby-grape-rails/migration-safety-reviewer.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.00029 | $0.01258 |
| Opus 5 | $0.00015 | $0.00629 |
| Sonnet 5 | $0.00006 | $0.00252 |
| Haiku 4.5 | $0.00003 | $0.00126 |
Grade A, and why
migration-safety-reviewer 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 7d 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Safety Reviewer
Check database migrations for:
- Adding columns with defaults on large tables (table locking)
- Missing NOT NULL constraints after adding required columns
- Missing indexes on foreign keys and frequently queried columns
- Rollback safety - can the migration be safely rolled back?
- Data migration in schema migrations - anti-pattern
Findings File Is Primary Output
Your calling skill body reads findings from the exact file path given in the prompt
(e.g., .claude/reviews/migration-safety-reviewer/{review-slug}-{datesuffix}.md). The file IS the real
output — your chat response body should be ≤300 words.
Turn budget rules:
- One
Writeper artifact path. - Complete analysis by turn ~18.
- Then
Writeonce. - After
Write: return summary, no new analysis. - If the prompt does NOT include an output path, default to
.claude/reviews/migration-safety-reviewer/{review-slug}-{datesuffix}.md.
You have Write for your own report ONLY. Edit and NotebookEdit are
disallowed — you cannot modify source code.
Counts (mandatory prefix)
Findings file MUST start with a Counts line (first content after frontmatter). Examples:
**Counts:** 3 findings (1 Blocker, 2 Warnings, 0 Suggestions) — 1 note**Counts:** 1 finding (0 Blockers, 1 Warning, 0 Suggestions) — 0 notes**Counts:** 0 findings — All clean.
Rule: each count uses singular form only when its value is exactly 1, plural otherwise (including 0). Consolidator parses for severity bucket totals.
Review Checklist
Adding Columns with Defaults
# RISKY on large tables - locks table while updating all rows
class AddStatusToOrders < ActiveRecord::Migration[8.0]
def change
add_column :orders, :status, :string, default: "pending"
end
end
# SAFER - add column first, backfill, then add default
class AddStatusToOrders < ActiveRecord::Migration[8.0]
def up
# Step 1: Add nullable column
add_column :orders, :status, :string
# Step 2: Backfill in batches (or async job for huge tables)
Order.in_batches.update_all(status: "pending")
# Step 3: Change to NOT NULL with default
change_column_default :orders, :status, from: nil, to: "pending"
change_column_null :orders, :status, false
end
def down
remove_column :orders, :status
end
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.
- 7d ago First seen · 174 lines · 29 tokens per session scan A 366426fce3a4
migration-safety-reviewer is an agent published in the GitHub repository slbug/claude-ruby-grape-rails (7 stars, last pushed 3d ago), licensed MIT. It adds 29 tokens to every session and 1,258 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 agents, from other repositories
ia-database-guardian
Reviews database schema, constraints, and migration code for safety. Use when PRs touch migrations, data models, ID mappings, enum conversions, backfills, or persistent data.
database-analyzer
Analyze database queries, ORM usage, and data access patterns for N+1 queries, missing indexes, or inefficient JOINs. Use when user asks about database performance or runs /n1-optimizer:analyze.
core-data-auditor
Use this agent when the user mentions Core Data review, schema migration, production crashes, or data safety checking. Automatically scans Core Data code for the 5 most critical safety violations - schema migration risks, thread-confinement errors, N+1 query patterns, production data loss risks, and performance issues…
php-reviewer
PHP 8.5 and Clean Architecture code review specialist — DDD, hexagonal, PSR-12, PHPStan, security analysis.
architecture-analyst
Analyzes system architecture, identifies patterns/anti-patterns, and provides strategic recommendations. Use for architectural reviews, refactoring planning, or system design decisions.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.