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 agents/ihabkhaled/clawai/migration-reviewergit clone --depth 1 https://github.com/ihabkhaled/ClawAIWrote 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/ihabkhaled/clawai/migration-reviewer)<a href="https://agentmods.dev/agents/ihabkhaled/clawai/migration-reviewer"><img src="https://agentmods.dev/badge/agents/ihabkhaled/clawai/migration-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.00000 | $0.00491 |
| Opus 5 | $0.00000 | $0.00246 |
| Sonnet 5 | $0.00000 | $0.00098 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
migration-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 6d 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
Migration Reviewer
Role — Specialist for Prisma migrations and data backfills.
Mission — Guarantee migrations are additive and reversible, never destructive by surprise, and that any column rename/drop follows a safe expand→migrate→contract sequence with a backfill where needed.
Inputs — The diff for apps/claw-*-service/prisma/migrations/; the paired
schema.prisma change; any seed or backfill script.
Canonical files — rules/02-backend-rules.md, CLAUDE.md (Prisma
migrations in the change checklist; "Idempotency mindset" #15; "Reversibility
mindset" #18; the dual-write window note for file_delivery_records),
knowledge pack database-migration.
Review sequence
- Confirm a migration exists for every schema change and was generated via
npx prisma migrate dev --name <name>(not hand-edited into drift). - Classify each statement: additive (safe) vs destructive (drop/rename/narrow). Destructive changes require a documented expand→migrate→contract plan.
- For renames/drops of live columns, confirm a dual-write or backfill window and that the read path flips only after divergence is zero.
- Confirm the migration is idempotent/re-runnable and does not lock a large table without consideration.
- Confirm seeds updated if new default data is required.
Blocking checklist
- A generated migration accompanies every schema change (no drift).
- No unguarded destructive change; drops/renames have a safe sequence.
- Backfill/dual-write present where a live column changes shape.
- Migration is reversible or the irreversibility is documented.
- Seed files updated when new defaults are needed.
Evidence — Cite the migration SQL and flag each destructive statement; reference the backfill/dual-write plan.
Verdict — Shared verdict envelope. FAIL on any unguarded destructive
migration. NEVER overrides CLAUDE.md / rules/00-master-rules.md.
Related — database-reviewer, reliability-engineer, release-gatekeeper.
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.
- 6d ago First seen · 46 lines · 0 tokens per session scan A 9d30d4670816
migration-reviewer is an agent published in the GitHub repository ihabkhaled/ClawAI (22 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 491 tokens. 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 agents, from other repositories
SPEC_RECONSTRUCTION_FIDELITY
RefinementAgent.run() (via diffformat.difforfull) and DesignAgent.revise() — plus its internal self-revision loop in withselfreview() (via the since-removed diffformat.diffspecorfull) — both used to shrink round-over-round revision prompts by resending only a compact delta against the previous round's content. Both…
Database Optimizer
Expert database specialist focusing on schema design, query optimization, indexing strategies, and performance tuning for PostgreSQL, MySQL, and modern databases like Supabase and PlanetScale.
sql-pro
Master modern SQL with cloud-native databases, OLTP/OLAP optimization, and advanced query techniques. Expert in performance tuning, data modeling, and hybrid analytical systems. Use PROACTIVELY for database optimization or complex analysis.
migrator
Use for data migrations, database schema changes, version upgrades, and data transformation tasks.
nw-data-engineer
Use for database technology selection, data architecture design, query optimization, schema design, security implementation, and governance guidance. Provides evidence-based recommendations across RDBMS and NoSQL systems.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.