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 skills/ivegamsft/basecoat/database-migrationnpx skills add ivegamsft/basecoat --skill database-migrationgit clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/database-migration)<a href="https://agentmods.dev/skills/ivegamsft/basecoat/database-migration"><img src="https://agentmods.dev/badge/skills/ivegamsft/basecoat/database-migration.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.00090 | $0.00417 |
| Opus 5 | $0.00045 | $0.00209 |
| Sonnet 5 | $0.00018 | $0.00083 |
| Haiku 4.5 | $0.00009 | $0.00042 |
Grade A, and why
database-migration 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 2d 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
Database Migration
Zero-downtime schema migration, versioning, and rollback for production databases.
Reference Files
| File | Contents |
|---|---|
references/zero-downtime-patterns.md |
Expand-contract phases, blue-green cutover, rollback strategies |
references/schema-versioning.md |
Flyway structure, migration format, undo scripts, CI/CD |
references/operations-checklist.md |
Pre-migration checklist, monitoring metrics, quick-start steps |
references/entra-sql-auth.md |
Entra-only auth, managed identity connection strings, common errors |
Key Patterns
| Pattern | Rule |
|---|---|
| Expand-contract | Add column → migrate data → drop old column across 3 separate deploys |
| Blue-green | Two identical DBs; switch traffic after 24–48 h; keep Blue ≥30 days |
| Dual-write | Write to both DBs; read from primary; zero data loss rollback |
| Flyway undo | U{version}__rollback.sql paired with every V{version}__migrate.sql |
| Validate first | Run flyway validate in CI before every flyway migrate |
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.
- 2d ago First seen · 35 lines · 90 tokens per session scan A d4d6e2221d61
database-migration is a skill published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 90 tokens to every session and 417 once invoked, about $0.0005 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
build-with-tinybase
Scaffold, extend, and verify reactive local-first JavaScript or TypeScript applications with TinyBase. Use when choosing TinyBase for in-memory tabular or key-value state, generating an app with create-tinybase, adding schemas or UI bindings, configuring browser or database persistence, configuring MergeableStore…
513-frameworks-micronaut-db-migrations-flyway
Use when you need to add or review Flyway database migrations in a Micronaut application — micronaut-flyway, db/migration scripts, flyway.datasources. configuration, and alignment with JDBC or Micronaut Data. This should trigger for requests such as Add or review Flyway migrations in a Micronaut project; Configure…
neon
Use when you have picked Neon (serverless Postgres) and need to connect correctly from a serverless or edge runtime, wire database branching into dev, preview and CI, or stop being burned by scale-to-zero cold starts and pooler limits — including choosing HTTP versus WebSocket connections and pooled versus direct…
planetscale-vitess-safety-review
Review a PlanetScale Vitess database for safe migrations, deploy requests, schema recommendations, Insights, webhooks, and operational safety.
planetscale-webhook-automation-recommendations
Recommend webhook subscriptions and safe automation patterns for PlanetScale alerts, anomalies, schema recommendations, deploy requests, and agent workflows.
database
Query and manage SQLite, PostgreSQL, and MySQL databases from the command line. Use when the user asks to run SQL queries, inspect database schemas, create or alter tables, import or export data, manage indexes, analyze query performance with EXPLAIN, back up or restore databases, or perform CRUD operations via…