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 lfyxhappy/lfcode --skill database-migrationgit clone --depth 1 https://github.com/lfyxhappy/lfcodeWrote 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/lfyxhappy/lfcode/database-migration)<a href="https://agentmods.dev/skills/lfyxhappy/lfcode/database-migration"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/database-migration/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/lfyxhappy/lfcode/database-migration"><img src="https://agentmods.dev/badge/skills/lfyxhappy/lfcode/database-migration.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.00056 | $0.00349 |
| Opus 5 | $0.00028 | $0.00175 |
| Sonnet 5 | $0.00011 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
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 3d 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
Treat schema and data changes as a rollout with compatibility and recovery requirements.
Workflow
- Identify the database, schema source, migration runner, environment, current version, affected tables, indexes, constraints, and data volume.
- Check repository instructions and worktree changes. Read neighboring migrations and the code paths that read and write the affected fields.
- Design an additive or otherwise compatible sequence where possible. Consider nullability, defaults, backfills, locking, transaction size, retries, idempotency, and concurrent old/new binaries.
- Define preflight checks, backup or restore evidence, failure detection, rollback or roll-forward recovery, and ownership before execution.
- Implement only the requested migration and required code compatibility changes. Use a dry run, disposable database, or staging target before a real target when available.
- Verify schema metadata, representative data invariants, application reads and writes, migration status, and performance after the change.
Boundaries
- Do not drop data, rewrite large tables, or run against production from an ambiguous request.
- Do not put credentials or complete data dumps in migrations, logs, tests, or the final report.
- Treat a migration file being accepted by the runner as insufficient proof that data and old clients remain safe.
Completion check
Report the preflight, rollout order, recovery path, verification evidence, and any environment or backup check that remains outstanding.
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.
- 3d ago First seen · 28 lines · 56 tokens per session scan A 32503f66f0d0
database-migration is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 6d ago), licensed MIT. It adds 56 tokens to every session and 349 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-09-05.
Other skills, from other repositories
gonavi-cli
Operate databases through the GoNavi headless CLI — the gonavi executable shipped in verified GitHub Release archives. Covers listing/adding/importing saved connections, running SQL queries against saved connections or ad-hoc connection files, exporting result sets to csv/json/md/html/xlsx, batch-executing SQL files…
feishu-bitable
A skill for managing Feishu Bitable, a database-like spreadsheet for organising structured records. It supports tables, fields, views, filters, and bulk changes.
supabase
Complete guide for the Supabase plugin — Management API access for running SQL queries, listing projects, managing edge functions, secrets, migrations, and inspecting project health.
backend-architect
Becomes a senior backend architect who designs scalable, resilient server-side systems with clear API contracts, sound data models, and documented trade-offs. Use when the user needs system design, database architecture, API contract definition, caching strategy, or backend technology selection. Do NOT use when…
mysql
Query the connected MySQL/MariaDB database with the mysql client. Use when the user asks about their database, tables, rows, schema, or to run SQL against MySQL.
postgres
Query the connected PostgreSQL database with psql. Use when the user asks about their database, tables, rows, schema, or to run SQL against Postgres.