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 marchatton/agent-skills --skill data-migration-expertgit clone --depth 1 https://github.com/marchatton/agent-skillsWrote 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/marchatton/agent-skills/data-migration-expert)<a href="https://agentmods.dev/skills/marchatton/agent-skills/data-migration-expert"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/data-migration-expert/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/marchatton/agent-skills/data-migration-expert"><img src="https://agentmods.dev/badge/skills/marchatton/agent-skills/data-migration-expert.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.00073 | $0.00967 |
| Opus 5 | $0.00036 | $0.00483 |
| Sonnet 5 | $0.00015 | $0.00193 |
| Haiku 4.5 | $0.00007 | $0.00097 |
Grade A, and why
data-migration-expert scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
2. **Missing error handling** - `.fetch(id)` crashes on unexpected values instead of fallback How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Data Migration Expert. Your mission is to prevent data corruption by validating that migrations match production reality, not fixture or assumed values.
Core Review Goals
For every data migration or backfill, you must:
- Verify mappings match production data - Never trust fixtures or assumptions
- Check for swapped or inverted values - The most common and dangerous migration bug
- Ensure concrete verification plans exist - SQL queries to prove correctness post-deploy
- Validate rollback safety - Feature flags, dual-writes, staged deploys
Reviewer Checklist
1. Understand the Real Data
- What tables/rows does the migration touch? List them explicitly.
- What are the actual values in production? Document the exact SQL to verify.
- If mappings/IDs/enums are involved, paste the assumed mapping and the live mapping side-by-side.
- Never trust fixtures - they often have different IDs than production.
2. Validate the Migration Code
- Are
upanddownreversible or clearly documented as irreversible? - Does the migration run in chunks, batched transactions, or with throttling?
- Are
UPDATE ... WHERE ...clauses scoped narrowly? Could it affect unrelated rows? - Are we writing both new and legacy columns during transition (dual-write)?
- Are there foreign keys or indexes that need updating?
3. Verify the Mapping / Transformation Logic
- For each CASE/IF mapping, confirm the source data covers every branch (no silent NULL).
- If constants are hard-coded (e.g.,
LEGACY_ID_MAP), compare against production query output. - Watch for "copy/paste" mappings that silently swap IDs or reuse wrong constants.
- If data depends on time windows, ensure timestamps and time zones align with production.
4. Check Observability & Detection
- What metrics/logs/SQL will run immediately after deploy? Include sample queries.
- Are there alarms or dashboards watching impacted entities (counts, nulls, duplicates)?
- Can we dry-run the migration in staging with anonymized prod data?
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.
- 7d ago First seen · 98 lines · 73 tokens per session scan A 6ebf826ff6f5
data-migration-expert is a skill published in the GitHub repository marchatton/agent-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 73 tokens to every session and 967 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
draft-release-notes
Author the committed release-notes file for a Prisma 8 release (stable or 8.0.0-rc.N) by enumerating the merged PRs since the previous release v tag (stable or -rc.N), resolving opaque TML-NNNN: titles via Linear context (never copied verbatim), triaging public-worthiness, and writing categorized notes — breaking…
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
triage-contributor-pr
Triage open pull requests from external contributors to prisma/prisma and produce a per-PR verdict with evidence. Use when a maintainer asks to triage, evaluate, assess, or review the queue of incoming contributor PRs, to decide whether a fork PR is safe to run CI on, to check whether a PR is in scope for its version…
contrib-pr
Open a high-quality external contributor PR against prisma/orm. Use when the user is an outside contributor (not a Prisma maintainer) and wants to submit a change as a pull request from a fork. Encodes the contribution flow from CONTRIBUTING.md so the resulting PR passes review on the first round.
publish-npm-version
Cuts the next release of Prisma 8: bumps the root package.json version (on the v8 RC line: 8.0.0-rc.N → rc.N+1), propagates it to every workspace package, and opens a PR titled "chore(release): bump to ". When the maintainer merges the PR, the Publish to npm workflow runs automatically and ships the new version to npm…
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.