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 rpraharaj/forward-deployed-engineer --skill cutover-plangit clone --depth 1 https://github.com/rpraharaj/forward-deployed-engineerWrote 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/rpraharaj/forward-deployed-engineer/cutover-plan)<a href="https://agentmods.dev/skills/rpraharaj/forward-deployed-engineer/cutover-plan"><img src="https://agentmods.dev/badge/skills/rpraharaj/forward-deployed-engineer/cutover-plan.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.00108 | $0.02493 |
| Opus 5 | $0.00054 | $0.01247 |
| Sonnet 5 | $0.00022 | $0.00499 |
| Haiku 4.5 | $0.00011 | $0.00249 |
Grade A, and why
cutover-plan 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 8d 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 — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cutover plan
The moment the old thing stops and the new thing starts.
Why this exists
A deploy changes code. A cutover changes state, and state does not roll back cleanly. Once the new system has accepted a transaction the old one never saw, "just switch back" stops being a plan and becomes a data reconciliation project.
That asymmetry is why cutovers deserve a bigger artifact than deploys. The questions that decide whether one succeeds are almost entirely about the seam: what happens to records written during the switch, how you know the two systems agree, and precisely when you lose the ability to go back.
Most failed cutovers were not failures of the new system. They were failures to plan the twenty minutes in the middle.
When this applies
- Migration or replatform where data moves
- A legacy system being replaced
- Any go-live with a defined switchover moment
- Two systems that will briefly coexist
When it doesn't
- Ordinary deploys, even risky ones — that's
deploy-runbook - Code-only changes with no data movement
- Decommissioning something with no replacement — that's
decommission-plan
Prerequisites
- Locate the workspace:
FDE_WORKSPACE, else the charter Location, else.fde/, else../<repo>-fde/ .fde/traces/data-model.md— you must know the eras and shapes before moving data.fde/06-blast-radius-*.md— every consumer of both systems.fde/07-verification.md— the new system proven on its own before you plan the swapdb-change-managementwhere schema changes are involved
Procedure
1. Choose the cutover shape
The single most consequential decision, and it should be explicit rather than defaulted into:
| Shape | How it works | Use when |
|---|---|---|
| Big bang | Stop old, migrate, start new | Small data, a real outage window is available, rollback is genuinely feasible |
| Parallel run | Both process everything; old is authoritative until proven | Correctness matters more than speed; you can afford double-writing |
| Phased by segment | Migrate tenants, regions, or product lines in tranches | Data partitions cleanly; blast radius must stay small |
| Strangler | Route by route, over months | Long-lived, low-risk, no single moment |
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.
- 8d ago First seen · 198 lines · 108 tokens per session scan A f00d98e82944
cutover-plan is a skill published in the GitHub repository rpraharaj/forward-deployed-engineer (6 stars, last pushed 21d ago), licensed MIT. It adds 108 tokens to every session and 2,493 once invoked, about $0.0005 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
runpod
Cloud GPU processing via RunPod serverless. Use when setting up RunPod endpoints, deploying Docker images, managing GPU resources, troubleshooting endpoint issues, or understanding costs. Covers all 5 toolkit images (qwen-edit, realesrgan, propainter, sadtalker, qwen3-tts).
memstack-deployment-domain-ssl
Use this skill when the user says 'setup domain', 'configure DNS', 'SSL certificate', 'domain-ssl', 'custom domain', 'HTTPS setup', or needs to configure DNS records, SSL certificates, and custom domains for any hosting provider. Do NOT use for full deployment workflows.
memstack-deployment-railway-deploy
Use this skill when the user says 'deploy to Railway', 'Railway setup', 'railway-deploy', or needs to deploy a Node.js, Python, or Docker application to Railway with environment variables, custom domains, and monitoring. Do NOT use for Netlify, Vercel, or Hetzner deployments.
project-tooling
Standard CLI tools for project infrastructure management.
deploy-gen
Generate deployment configurations (Docker, Kubernetes) for the current project.
ring:creating-grafana-dashboards
Authoring Grafana dashboards for Go services instrumented with lib-observability telemetry (tracing, metrics, log), plus a reference mode for RED/USE panel patterns and Grafonnet templates. Sweep mode inventories telemetry, runs PM deliberation on themes/SLIs/alerts, authors Grafonnet libsonnet compiled to JSON, and…