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/m-binimran/dev-pack/migration-safetynpx skills add m-binimran/dev-pack --skill migration-safetygit clone --depth 1 https://github.com/m-binimran/dev-packWhat 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.00050 | $0.00379 |
| Opus 5 | $0.00025 | $0.00189 |
| Sonnet 5 | $0.00010 | $0.00076 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
migration-safety 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
migration-safety
Every migration must be reversible and must not lock a busy table or drop data by surprise.
(The migration-validate hook checks your output — design to pass it.)
Always produce a pair
up: the change.down: the exact rollback. If a change is truly irreversible (dropping data), say so loudly and require explicit confirmation.
Expand → backfill → contract (for column changes)
- Expand: add the new column/table, nullable, no constraint. Cheap, non-locking.
- Backfill: populate in batches (
update ... where id between ...), not one giant statement. - Contract: add the
NOT NULL/constraint and drop the old column — in a later migration, after the app writes both.
Locking traps to avoid
ADD COLUMN ... NOT NULLwith noDEFAULTon a non-empty table → fails / full rewrite. Add a default.ALTER COLUMN TYPE→ rewrites + locks. Prefer add-new-column + backfill.- Creating an index on a hot table → use
CREATE INDEX CONCURRENTLY(outside a txn).
Output
upSQL,downSQL, and a one-line risk note (lock risk / data-loss risk / safe).- For destructive steps, an explicit "this cannot be undone" line.
Guardrails
- No migration without a rollback path.
- Never combine a destructive drop with the additive change in the same migration — separate them.
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 · 34 lines · 50 tokens per session scan A 3c6718230d44
migration-safety is a skill published in the GitHub repository m-binimran/dev-pack (2 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 379 once invoked, about $0.0003 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
db-repair
Auto-fix gbrain's Postgres access so the brain stays available. When any gbrain command or MCP tool result carries a GBRAINDBACCESS marker (or an operator reports the brain database is down), run the hardcoded gbrain db-repair ladder: diagnose, apply the safe tier, verify. The action is ALWAYS the hardcoded command …
postgres-pro
Use when optimizing PostgreSQL queries, configuring replication, or implementing advanced database features. Invoke for EXPLAIN analysis, JSONB operations, extension usage, VACUUM tuning, performance monitoring.
postgres-database-migration
Use this skill for planning, testing, and safely executing PostgreSQL schema migrations — especially when working with production data or shared databases. Trigger when user asks to: Test a schema migration before applying it to production Add, remove, or rename columns safely on a live table Change a column's data…
setup-timescaledb-hypertables
Use this skill when creating database schemas or tables for Timescale, TimescaleDB, TigerData, or Tiger Cloud, especially for time-series, IoT, metrics, events, or log data. Use this to improve the performance of any insert-heavy table. Trigger when user asks to: Create or design SQL schemas/tables AND…
claimable-postgres
Provision instant temporary Postgres databases via Claimable Postgres by Neon (neon.new) with no login, signup, or credit card. Supports REST API, CLI, and SDK. Use when users ask for a quick Postgres environment, a throwaway DATABASEURL for prototyping/tests, or "just give me a DB now". Triggers include: "quick…
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…