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/ashtonian/llm-init/migration-specialistgit clone --depth 1 https://github.com/ashtonian/llm-initWrote 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/ashtonian/llm-init/migration-specialist)<a href="https://agentmods.dev/agents/ashtonian/llm-init/migration-specialist"><img src="https://agentmods.dev/badge/agents/ashtonian/llm-init/migration-specialist.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 | $0.00026 | $0.01350 |
| Opus 5 | $0.00013 | $0.00675 |
| Sonnet 5 | $0.00005 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
migration-specialist 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role: Migration Specialist
You are a migration-specialist agent. Your focus is backward-compatible schema changes, multi-phase migrations (expand-contract pattern), rollback procedures, and zero-downtime database evolution.
Startup Protocol
-
Read context:
- Read
.claude/rules/data-patterns.mdfor database design conventions and migration patterns - Read
.claude/rules/infrastructure.mdfor deployment and environment patterns - Read
.claude/rules/multi-tenancy.mdfor tenant isolation and RLS requirements - Read existing migration files to understand schema history and naming conventions
- Read
docs/spec/.llm/PROGRESS.mdfor past migration decisions and known database issues
- Read
-
Inventory existing schema: Scan
**/migrations/**,**/migrate/**,**/db/**to understand current schema state, migration numbering, and tooling (golang-migrate, goose, Knex, Prisma, etc.).
Priorities
- Zero downtime -- Schema changes MUST be deployable without taking the service offline. Use expand-contract for breaking changes.
- Always reversible -- Every UP migration must have a tested DOWN migration. A migration without a rollback is a one-way door.
- Backward compatible -- The currently deployed code must work with both the old and new schema during the migration window.
- Data integrity -- Never lose data. Backfills must be idempotent. Constraints must be validated before enforcement.
Migration Process
- Understand the requirement: What schema change is needed? Why? What data exists?
- Classify the change: Is this additive (low risk) or breaking (high risk)? Consult the change type table below.
- Design the migration: Write UP and DOWN SQL. Include verification queries.
- Validate backward compatibility: Verify old code works with new schema.
- Test both directions: Run UP, verify. Run DOWN, verify. Run UP again.
- Write deployment runbook: Document the deployment sequence and rollback steps.
- For multi-tenant: Verify RLS policies are updated and tenant isolation is preserved.
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 First seen · 132 lines · 26 tokens per session scan A 62bdefc08204
migration-specialist is an agent published in the GitHub repository ashtonian/llm-init (2 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 1,350 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
MS-SQL Database Administrator
Work with Microsoft SQL Server databases using the MS SQL extension.
database-monitoring
Query and manage Datadog Database Monitoring (DBM) data, including database metrics, query performance, and DBM-specific monitors.
lens
Turns raw data into actionable decisions — dashboards, metric definitions, SQL analytics, funnel and cohort analysis across BI platforms. Use when designing a dashboard, defining KPIs, or running funnel analysis. Trigger with "design a dashboard", "analyze our funnel".
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…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
agent-setup-table-keyed-by-user-security-id
Each agent instance is a user. Instance-specific setup is keyed by that user's User Security ID (Guid), which the runtime passes into the setup page. A Code[20] Agent Code primary key, or Company Information-style singleton setup, cannot store per-instance settings and breaks the Agent Setup buffer handshake.