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 skills add The-AI-Directory-Company/agents-and-skills --skill database-migration-plangit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/skills/the-ai-directory-company/agents-and-skills/database-migration-plan)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/database-migration-plan"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/database-migration-plan/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/skills/the-ai-directory-company/agents-and-skills/database-migration-plan"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/database-migration-plan.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.00046 | $0.01569 |
| Opus 5 | $0.00023 | $0.00785 |
| Sonnet 5 | $0.00009 | $0.00314 |
| Haiku 4.5 | $0.00005 | $0.00157 |
Grade A, and why
database-migration-plan 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 9d 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Database Migration Plan
Before you start
Gather the following from the user:
- What schema change is needed? (Add column, rename column, change type, add/drop index, create/drop table, split table)
- Which database engine? (PostgreSQL, MySQL, SQL Server, or engine-agnostic)
- Is zero-downtime required? (Can the application tolerate maintenance windows?)
- What is the table size? (Row count and data size — this determines strategy)
- Are there dependent applications? (Other services reading/writing this table)
- What ORM or migration tool is in use? (Prisma, Drizzle, Knex, Flyway, Alembic, ActiveRecord, raw SQL)
If the user says "add a column to the users table," push back: "How many rows? Is the app deployed with zero-downtime requirements? Is the column nullable or does it need a default? Other services reading this table?"
This skill covers schema-level DDL changes. For moving data between systems or ETL pipelines, see the data-migration-plan skill instead.
Procedure
Step 1: Classify the migration risk
| Change type | Lock risk | Data risk | Typical approach |
|---|---|---|---|
| Add nullable column | Low | None | Single migration |
| Add column with default | Medium (engine-dependent) | None | Check engine behavior |
| Add index | Medium-High | None | CREATE INDEX CONCURRENTLY |
| Drop column | Low | High (data loss) | Multi-phase |
| Rename column | High | Medium | Multi-phase with alias |
| Change column type | High | High | Multi-phase with dual-write |
| Drop table | Low | High (data loss) | Multi-phase with grace period |
| Split/merge tables | High | High | Multi-phase with dual-write |
For medium or high risk changes, use the multi-phase approach in Step 3.
Step 2: Write the migration script
Every migration must have an up and down script:
-- Migration: 20240115_001_add_status_to_orders
-- Description: Add status column to orders table for fulfillment tracking
-- UP
ALTER TABLE orders ADD COLUMN status VARCHAR(32) NULL;
-- DOWN
ALTER TABLE orders DROP COLUMN status;
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 131 lines · 46 tokens per session scan A bc36ee9c2610
database-migration-plan is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 46 tokens to every session and 1,569 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
database-expert
Advanced database design and administration for PostgreSQL, MongoDB, and Redis. Use when designing schemas, optimizing queries, managing database performance, or implementing data patterns.
generic-fullstack-feature-developer
Guide feature development for full-stack applications with architecture focus. Covers Next.js App Router patterns, NestJS backend services, database models, data workflows, and seamless integration. Use when adding new features, refactoring existing code, or planning major changes.
api-baas-firebase
Firebase backend-as-a-service — Firestore, Authentication, Cloud Functions v2, Storage, Hosting, Admin SDK, security rules, emulator suite.
api-database-mongodb
Native MongoDB driver (the mongodb npm package) - MongoClient lifecycle, typed collections, CRUD result shapes, cursors, aggregation pipelines, index design, transactions.
api-baas-neon
Serverless PostgreSQL with branching, autoscaling, and edge-compatible driver.
api-baas-planetscale
Serverless MySQL platform with branching, deploy requests, and edge-compatible driver.