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 data-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/data-migration-plan)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/data-migration-plan"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/data-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/data-migration-plan"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/data-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.00037 | $0.01578 |
| Opus 5 | $0.00018 | $0.00789 |
| Sonnet 5 | $0.00007 | $0.00316 |
| Haiku 4.5 | $0.00004 | $0.00158 |
Grade A, and why
data-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 — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Migration Plan
Before you start
Gather the following from the user. If any is missing, ask before proceeding:
- Current schema — Tables, columns, relationships, and storage engine. Include indexes and constraints.
- Target schema — The desired end state. What changes: renamed columns, split tables, new relationships, type changes?
- Data volume — Row counts for affected tables, total size on disk, and growth rate.
- Downtime tolerance — Zero-downtime required? Maintenance window available? If so, how long?
- Rollback requirements — How quickly must you revert? Is data loss during rollback acceptable? What is the point-of-no-return?
If the user says "just rename a column," push back: What reads from this column? Are there cached references? Is the column in any API contract, event payload, or downstream ETL?
Migration plan template
Use the following structure. Every phase includes explicit entry criteria, steps, and exit criteria.
Pre-Migration Assessment
Before writing any migration code:
- Catalog every service, job, and query that reads or writes the affected tables
- Identify foreign key dependencies and cascade behavior
- Measure current query performance on affected tables (baseline P50/P99)
- Estimate migration duration: run the backfill query against a production-sized replica
- Confirm backup and restore procedures work — test the restore, not just the backup
Phase 1: Dual-Write
Goal: New writes go to both old and new schema without affecting reads.
- Deploy schema changes additively (new columns, new tables) — never drop or rename yet
- Update write paths to populate both old and new locations
- Add logging to confirm dual-write consistency (compare old vs. new on every write)
- Integrity check: Query for rows where old and new values diverge. Count must be zero before proceeding.
Rollback trigger: If dual-write error rate exceeds 0.1%, disable new write path and revert deployment.
What ships with it
5 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 · 124 lines · 37 tokens per session scan A bbbf23f3d293
data-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 37 tokens to every session and 1,578 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.