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 vaquarkhan/data-engineering-agent-skills --skill data-migration-and-platform-cutovergit clone --depth 1 https://github.com/vaquarkhan/data-engineering-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/vaquarkhan/data-engineering-agent-skills/data-migration-and-platform-cutover)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/data-migration-and-platform-cutover"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-migration-and-platform-cutover/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/vaquarkhan/data-engineering-agent-skills/data-migration-and-platform-cutover"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/data-migration-and-platform-cutover.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.00048 | $0.00503 |
| Opus 5.5 | $0.00019 | $0.00201 |
| Sonnet 5.5 | $0.00010 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00050 |
Grade A, and why
data-migration-and-platform-cutover 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 1mo 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Migration And Platform Cutover
Overview
Use this skill when the system is changing platforms or major architectural boundaries. It helps agents plan parallel runs, compatibility layers, validation, and safe cutover rather than treating migration as a one-day switch.
When to Use
- migrating from one warehouse or lakehouse to another
- moving pipelines between orchestration or compute systems
- replatforming storage formats or table engines
- performing major serving-layer cutovers
Do not start cutover work without a rollback and validation path.
Workflow
-
Define the migration scope. Include:
- source platform
- target platform
- affected datasets and jobs
- compatibility expectations
- cutover window
-
Choose the migration pattern. Common patterns:
- parallel run
- shadow validation
- phased consumer cutover
- bulk migration plus freeze window
-
Define validation gates. Typical gates:
- row counts
- metric reconciliation
- freshness parity
- schema compatibility
- performance or cost acceptance
-
Make rollback real. Rollback should be executable, not a sentence in a plan.
-
Retire the old path deliberately after confidence is established.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "We can switch everything at once during a quiet window." | Hidden downstream dependencies often make big-bang cutovers fragile. |
| "If the data matches once, we are done." | Cutovers also need sustained operational parity and recovery confidence. |
| "We can keep the old path around indefinitely just in case." | Zombie dual paths create confusion and extra risk unless retired deliberately. |
Red Flags
- rollback is not executable
- consumer cutover is assumed rather than coordinated
- validation is limited to a one-time row count
- the old and new systems are both considered source-of-truth after cutover
Verification
- Migration scope and target behavior are explicit
- The cutover pattern and validation gates are documented
- Rollback is real and tested where practical
- Old-path retirement is planned after stable adoption
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.
- 1mo ago First seen · 72 lines · 48 tokens per session scan A 7e5e160e6515
data-migration-and-platform-cutover is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (59 stars, last pushed 4mo ago), licensed MIT. It adds 48 tokens to every session and 503 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
qdrant-managed-cloud-quickstart
Getting a first Qdrant Managed Cloud cluster running and connected safely: Free, Standard, and Premium tiers, choices that can't be changed later, creating clusters from the Console or the qcloud CLI, Database API keys, ports and TLS, strict mode on new collections, Cloud Inference, and what to set before relying on a…
qdrant-vertical-scaling
Guides Qdrant vertical scaling decisions. Use when someone asks 'how to scale up a node', 'need more RAM', 'upgrade node size', 'vertical scaling', 'resize cluster', 'scale up vs scale out', or when memory/CPU is insufficient on current nodes. Also use when someone wants to avoid the complexity of horizontal scaling.
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.
plan-backup-dr
Audit whether a project can actually recover from data loss — not just whether backups exist — then emit a phased DR plan. Use when "can we recover if the DB dies", "audit our backups", "what's our RPO/RTO", or "disaster recovery". Plan only. Destructive-op gates stay on plan-data-integrity.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…
snowflake-provision-environment
Provision the migration environment inside AIDP for the prod flow - the workspace (name auto-translated to the simplest safe charset), the migration-assets compute cluster, optional cluster libraries from requirements-aidp.txt, the backup-snowflake-migration/ workspace folder holding the data-migration scripts and the…