ops-migrate

ops-migrate is a command for Claude Code from christopherlouet/claude-base. It costs 0 tokens per session (257 once invoked), scanned A, original, MIT.

A planning assistant for migrating code, dependencies, database schemas, or data from one state to another. It emphasizes incremental changes, testing, backups, and a rollback plan.

In plain words
What is it for?
Use it to plan and carry out dependency upgrades, code changes, schema changes, or data migrations, including staging validation and rollback steps.
Why use it?
It reduces the risk of breaking an application or losing data during a migration. The step-by-step plan makes affected files, risks, checks, and recovery commands explicit.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to plan and carry out dependency upgrades, code changes, schema changes, or data migrations, including staging validation and rollback steps.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/christopherlouet/claude-base/ops-migrate
Install

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.

Clone the repo
git clone --depth 1 https://github.com/christopherlouet/claude-base

Made for: Claude Code.

Wrote 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.

agentmods badge for ops-migrate

README.md
[![agentmods](https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-migrate/github.svg)](https://agentmods.dev/commands/christopherlouet/claude-base/ops-migrate)
Your own site
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-migrate"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-migrate/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.

agentmods 80×15 button for ops-migrate

Your own site · 80×15
<a href="https://agentmods.dev/commands/christopherlouet/claude-base/ops-migrate"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/ops-migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 257 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00257
Opus 5.5 $0.00000 $0.00103
Sonnet 5.5 $0.00000 $0.00051
Haiku 4.5 $0.00000 $0.00026

Measured 1mo ago against content hash baa9ccc6fab2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ops-migrate 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.

.claude/commands/ops/ops-migrate.md · 46 lines

What it actually says

Migrate

Migration of code, dependencies or data.

Request context

$ARGUMENTS

Objective

Plan and execute a secure migration with a rollback plan, whether for dependencies, code, schema or data.

Workflow

  • Identify the type of migration (dependencies, major version, code, schema)
  • Document the current state and identify all occurrences
  • Plan migration steps with impact estimation
  • Prepare the rollback plan
  • Execute in incremental steps (modify, test, commit)
  • Validate (tests pass, build OK, manual smoke tests)
  • Apply secure migration techniques if necessary (Strangler Fig, Feature Flags, Codemods)

Expected output

  1. Migration plan: steps, impacted files, risk
  2. Migration checklist per step
  3. Rollback plan with commands
Agent Usage
/ops:ops-database Schema migrations
/ops:ops-backup Backup before migration
/ops:ops-deps Dependency migration

IMPORTANT: Always have a tested rollback plan.

IMPORTANT: Small commits, incremental migrations.

YOU MUST back up data before any migration.

NEVER migrate to production without having tested in staging.

Changes

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.

  1. 1mo ago First seen · 46 lines · 0 tokens per session scan A baa9ccc6fab2

Subscribe to this mod's changes

ops-migrate is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 257 tokens. 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-03.