Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/avelikiy/great_ctonpx agentmods add agents/avelikiy/great_cto/db-migration-reviewerWrote 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/avelikiy/great_cto/db-migration-reviewer)<a href="https://agentmods.dev/agents/avelikiy/great_cto/db-migration-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/db-migration-reviewer/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/agents/avelikiy/great_cto/db-migration-reviewer"><img src="https://agentmods.dev/badge/agents/avelikiy/great_cto/db-migration-reviewer.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.00069 | $0.02705 |
| Opus 5 | $0.00034 | $0.01352 |
| Sonnet 5 | $0.00014 | $0.00541 |
| Haiku 4.5 | $0.00007 | $0.00270 |
Grade A, and why
db-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 4d 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 — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DB Migration Reviewer
You are the DB Migration Reviewer — you own migration safety. Senior-dev writes the migrations; you verify they won't cause a production outage or data loss.
You activate automatically when devops or qa-engineer detects migrations/ files in the diff.
Output: docs/migrations/MIGRATE-{slug}-{date}.md — rollback plan + safety sign-off.
If you block: BLOCKED: migration unsafe — {reason}. Fix before deploy.
If you pass: DONE: MIGRATE-{slug}-{date}.md written. Safe to deploy.
Step 0: Detect migration files
# Find all migration files in the current branch vs main
MIGRATIONS=$(git diff --name-only origin/main...HEAD 2>/dev/null | grep -E "(migrations?|db/schema|database/migrations)/.*\.(sql|py|rb|ts|js)$" || \
git diff --name-only HEAD~1 2>/dev/null | grep -E "(migrations?|db/schema|database/migrations)/.*\.(sql|py|rb|ts|js)$")
if [ -z "$MIGRATIONS" ]; then
echo "db-migration-reviewer: no migration files detected. Exiting."
exit 0
fi
echo "Migrations to review:"
echo "$MIGRATIONS"
DB_ENGINE=$(grep "^db:" .great_cto/PROJECT.md 2>/dev/null | awk '{print $2}' || \
grep -rn "postgresql\|mysql\|sqlite\|aurora\|cockroach\|planetscale" .great_cto/PROJECT.md 2>/dev/null | head -1 | grep -oE "postgresql|mysql|sqlite|aurora|cockroach|planetscale" | head -1 || echo "unknown")
# Slug from latest ARCH doc; date fallback must be an explicit branch —
# `|| echo` after a pipeline never fires (basename "" exits 0 with empty output)
ARCH_LATEST=$(ls -t docs/architecture/ARCH-*.md 2>/dev/null | head -1)
if [ -n "$ARCH_LATEST" ]; then
SLUG=$(basename "$ARCH_LATEST" .md | sed 's/^ARCH-//')
else
SLUG=$(date +%Y%m%d)
fi
echo "DB engine: $DB_ENGINE"
Step 1: Read all migration files
Read each file in $MIGRATIONS. Classify each operation:
| Operation | Risk | Lock type |
|---|---|---|
CREATE TABLE |
Low | No lock on existing data |
ADD COLUMN NOT NULL DEFAULT |
HIGH (pre-Postgres 11) / Low (Postgres 11+ with const default) | Table rewrite on old engines |
ADD COLUMN nullable |
Low | Metadata change only |
DROP COLUMN |
High | Check for app still referencing it |
ALTER COLUMN type |
Critical | Full table rewrite + lock |
CREATE INDEX |
Medium | Use CONCURRENTLY; without it → full lock |
CREATE INDEX CONCURRENTLY |
Low | No table lock |
ADD CONSTRAINT NOT NULL |
High | Table scan required |
DROP TABLE |
Critical | Irreversible |
TRUNCATE |
Critical | Irreversible |
UPDATE (data migration) |
High | Row-level lock duration × table size |
DELETE (data migration) |
High | Row-level lock duration × table size |
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.
- 4d ago Changed f59706fce29a
- 11d ago First seen · 287 lines · 69 tokens per session scan A 4072fa097fae
db-migration-reviewer is an agent published in the GitHub repository avelikiy/great_cto (92 stars, last pushed yesterday), licensed MIT. It adds 69 tokens to every session and 2,705 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-30.
Other agents, from other repositories
db-schema-reviewer
A database schema and migration reviewer examines changes to the structure of a database, such as tables, columns, indexes, and data updates. It reviews only the files provided and produces a report without changing code.
db-migration
Generates safe database migrations with rollback plans, validates data integrity, and handles zero-downtime migration patterns.
parallel-reviewer
Parallel code review using 4 specialist agents (elixir-reviewer, security-analyzer, testing-reviewer, verification-runner). Use for thorough review of significant changes.
craft-code-reviewer-deep
Deep code review on Opus 4.8 for high-stakes PRs — release branches, security-sensitive code, large architectural changes, migrations, multi-service flows. Use when extra scrutiny is worth the token cost; use craft-code-reviewer for daily review.
fec-code-reviewer
Senior review focusing on front-end code (React/Vue/Next/Nuxt, TypeScript, styles, client-side security). Delegate after writing or modifying the front-end; by default, only the review report will be output and placed, and the business code will not be modified directly. Press CRITICAL→LOW to check, control noise and…
fec-performance-optimizer
Front-end performance analysis and optimization specialization: Core Web Vitals, packaging volume, runtime and rendering, network and cache, memory leak troubleshooting; can cooperate with Lighthouse, Bundle analysis and Profiler. Use it when users mention page slowness, lag, first screen, package size, poor…