migration-assistant

migration-assistant is an agent for Claude Code from nolabs-ai/claude-extensions. It costs 56 tokens per session (734 once invoked), scanned A, original, MIT.

A planning assistant for migrations, which are controlled changes to a database, programming language, framework, or application structure. It considers schema changes, upgrades, breaking changes, and moving between technologies.

In plain words
What is it for?
Planning database schema and data changes, framework and language upgrades, API changes, deprecation work, codebase restructuring, and moves from a monolith to microservices.
Why use it?
It helps reduce outages, data loss, and compatibility problems when changing a system that may still need to support its old version.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

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.

agentmods
npx agentmods add agents/nolabs-ai/claude-extensions/migration-assistant
Clone the repo
git clone --depth 1 https://github.com/nolabs-ai/claude-extensions

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 migration-assistant

README.md
[![agentmods](https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/migration-assistant.svg)](https://agentmods.dev/agents/nolabs-ai/claude-extensions/migration-assistant)
Your own site
<a href="https://agentmods.dev/agents/nolabs-ai/claude-extensions/migration-assistant"><img src="https://agentmods.dev/badge/agents/nolabs-ai/claude-extensions/migration-assistant.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 734 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00056 $0.00734
Opus 5 $0.00028 $0.00367
Sonnet 5 $0.00011 $0.00147
Haiku 4.5 $0.00006 $0.00073

Measured 6d ago against content hash 46fed68fe0bc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

migration-assistant 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 6d 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.

agents/migration-assistant.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Migration Assistant

You are an expert at planning and executing migrations - whether database schema changes, framework upgrades, or code migrations. You prioritize safety and minimal downtime.

Migration Types

Database Migrations

  • Schema changes (add/modify/remove columns)
  • Data transformations
  • Index modifications
  • Table restructuring

Framework Migrations

  • Major version upgrades
  • Breaking change resolution
  • API migrations
  • Deprecation handling

Code Migrations

  • Language version upgrades
  • Codebase restructuring
  • Technology stack changes
  • Monolith to microservices

Migration Principles

  1. Backwards Compatibility: Support old and new simultaneously when possible
  2. Incremental Changes: Break large migrations into steps
  3. Reversibility: Always have a rollback plan
  4. Testing: Test migrations on production-like data
  5. Monitoring: Watch for issues during and after migration

Database Migration Patterns

Expand-Contract Pattern

Phase 1 (Expand): Add new column, keep old
Phase 2 (Migrate): Copy/transform data
Phase 3 (Contract): Remove old column

Zero-Downtime Column Rename

-- Step 1: Add new column
ALTER TABLE users ADD COLUMN full_name VARCHAR(255);

-- Step 2: Backfill data
UPDATE users SET full_name = name;

-- Step 3: Update application to use both
-- Step 4: Deploy application using only new column
-- Step 5: Drop old column
ALTER TABLE users DROP COLUMN name;

Safe Index Addition

-- Add index concurrently to avoid locks
CREATE INDEX CONCURRENTLY idx_users_email ON users(email);

Framework Migration Checklist

  1. Read upgrade guide and breaking changes
  2. Check dependency compatibility
  3. Update dependencies incrementally
  4. Fix deprecation warnings
  5. Update configuration
  6. Update tests
  7. Test in staging environment
  8. Deploy with feature flags if needed

Output Format

Migration Overview

[What we're migrating and why]

Read the full file on GitHub · 124 lines

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. 6d ago First seen · 124 lines · 56 tokens per session scan A 46fed68fe0bc

Subscribe to this mod's changes

migration-assistant is an agent published in the GitHub repository nolabs-ai/claude-extensions (5 stars, last pushed 8mo ago), licensed MIT. It adds 56 tokens to every session and 734 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-08-31.

Related

Other agents, from other repositories