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/wojcikmm/spec-development-protocol/database-migrationnpx skills add WojcikMM/spec-development-protocol --skill database-migrationgit clone --depth 1 https://github.com/WojcikMM/spec-development-protocolWhat 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.00015 | $0.00270 |
| Opus 5 | $0.00008 | $0.00135 |
| Sonnet 5 | $0.00003 | $0.00054 |
| Haiku 4.5 | $0.00002 | $0.00027 |
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
Skill: Write Database Migration
Purpose
Produce a safe, reviewable, and reversible database schema change that can be deployed without downtime or data loss.
Prerequisites
- Data model change is defined in the technical design.
- ORM/migration tool is specified in
TECH.md.
Checklist
- One change per migration: Don't bundle unrelated schema changes. Name it clearly.
- Always provide a rollback: The change must be reversible.
- Non-nullable columns: Must have a
DEFAULTvalue or a backfill step. - Renaming: Use a multi-step expand-migrate-contract pattern. Do not rename and deploy in a single step.
- Index creation: Use
CONCURRENTLY(PostgreSQL) or equivalent to avoid table locks. - Backfills: Run in batches. Separate data migrations from schema migrations.
- Testing: Run the migration and its rollback locally before committing. Verify the schema diff and check for data loss.
Quality Bar
- Migration and rollback apply cleanly.
- No data loss occurs.
- CI runs the migration during the test pipeline.
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 · 32 lines · 15 tokens per session scan A ee08b1d29a10
database-migration is a skill published in the GitHub repository WojcikMM/spec-development-protocol (2 stars, last pushed 22d ago), licensed MIT. It adds 15 tokens to every session and 270 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 skills, from other repositories
prisma-upgrade-v7
Complete migration guide from Prisma ORM v6 to v7 covering all breaking changes. Use when upgrading Prisma versions, encountering v7 errors, or migrating existing projects. Triggers on "upgrade to prisma 7", "prisma 7 migration", "prisma-client generator", "driver adapter required".
ddia-systems
Design data systems by understanding storage engines, replication, partitioning, transactions, and consistency models. Use when the user mentions "database choice", "which database should I use", "SQL or NoSQL", "replication lag", "partitioning strategy", "consistency vs availability", "stream processing", "ACID…
sqlitecpp-update-sqlite
How to update the bundled SQLite3 amalgamation (sqlite3/sqlite3.c and sqlite3.h), the Meson wrap, README.md, and CHANGELOG.md. Use when upgrading SQLite, refreshing the vendored amalgamation, or bumping the sqlite3 wrap.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, FK…
mongodb-natural-language-querying
Generate read-only MongoDB queries (find) or aggregation pipelines using natural language, with collection schema context and sample documents. Use this skill whenever the user asks to write, create, or generate MongoDB queries, wants to filter/query/aggregate data in MongoDB, asks "how do I query...", needs help with…
sql-translate
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.).