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/ao92265/claude-code-playbook/migrate-dbnpx skills add ao92265/claude-code-playbook --skill migrate-dbgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/migrate-db)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/migrate-db"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/migrate-db.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.00066 | $0.00660 |
| Opus 5 | $0.00033 | $0.00330 |
| Sonnet 5 | $0.00013 | $0.00132 |
| Haiku 4.5 | $0.00007 | $0.00066 |
Grade A, and why
migrate-db 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 6d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safe Database Migration
Execute database schema migrations with safety checks at every step.
Steps
-
Pre-flight checks:
- Verify database connection: test credentials and connectivity
- Confirm target database and environment (dev/staging/prod)
- Check for pending migrations: list unapplied migrations
- Verify no other migrations are currently running
- ASK the user to confirm the target environment before proceeding
-
Review the migration:
- Read the migration file(s) to understand what changes will be made
- Identify destructive operations: DROP TABLE, DROP COLUMN, ALTER TYPE
- Flag any operations that will lock tables for extended periods
- Check for data migrations vs. schema-only changes
- Estimate impact: how many rows affected, expected duration
-
Backup verification:
- Confirm a recent backup exists (ask the user)
- For production: require explicit confirmation that backup was taken within the last hour
- For dev/staging: note that backup is recommended but not blocking
- Record the current schema state:
pg_dump --schema-onlyor equivalent
-
Dry run (if supported):
- Run migration with
--dry-runor--pretendflag if available - For SQL migrations: wrap in a transaction and ROLLBACK
- Review the dry-run output for unexpected changes
- Confirm output matches expected behavior
- Run migration with
-
Execute the migration:
- Run the migration command
- Monitor output for errors
- If migration fails partway: DO NOT retry automatically — report the state and ask the user
-
Post-migration verification:
- Run schema diff to confirm changes match expectations
- Execute smoke test queries to verify data integrity
- Check that the application can connect and basic operations work
- Run the application's test suite against the migrated database
-
Document the rollback plan:
- Write the exact commands needed to reverse the migration
- If migration is irreversible (data deletion), document what was lost
- Save rollback steps to a file for reference
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.
- 6d ago First seen · 71 lines · 66 tokens per session scan A 9324fdfb786c
migrate-db is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 19d ago), licensed MIT. It adds 66 tokens to every session and 660 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
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
sdk-design
Doctrine for designing and evolving any SDK Grida ships — TypeScript, Rust, or otherwise. "SDK" here means a surface that crosses a foreign-or-foreign-treated boundary: published packages, separately-versioned consumers, FFI bindings, public-by-design modules. An SDK's job is to refuse; a strict, honest surface…
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
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, foreign key…