migrate-architecture

migrate-architecture is a command for Claude Code from TheLobbi/claude. It costs 0 tokens per session (3,129 once invoked), scanned A, original, MIT.

A migration planner and executor for major changes to an application's architecture, including moving from a monolith to microservices, changing databases, moving to the cloud, or changing technologies.

In plain words
What is it for?
Use it to plan and carry out large architecture or infrastructure migrations while keeping rollback and service availability in view.
Why use it?
It organizes risky changes into phases with validation, monitoring, rollback plans, and data-consistency checks. Blue-green and canary deployments release changes gradually to reduce interruption.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Part of the claude-orchestration plugin — 6 skills, 133 commands, 9 agents, 8 hooks, 6 plugins shipped together

Good fit Use it to plan and carry out large architecture or infrastructure migrations while keeping rollback and service availability in view.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/thelobbi/claude/migrate-architecture
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/TheLobbi/claude

Made for: Claude Code.

Or install claude-orchestration, the plugin that ships this one along with the rest of its 6 skills, 133 commands, 9 agents, 8 hooks, 6 plugins.

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 migrate-architecture

README.md
[![agentmods](https://agentmods.dev/badge/commands/thelobbi/claude/migrate-architecture.svg)](https://agentmods.dev/commands/thelobbi/claude/migrate-architecture)
Your own site
<a href="https://agentmods.dev/commands/thelobbi/claude/migrate-architecture"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/migrate-architecture.svg" alt="Measured on agentmods" 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 3,129 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.03129
Opus 5 $0.00000 $0.01564
Sonnet 5 $0.00000 $0.00626
Haiku 4.5 $0.00000 $0.00313

Measured 2d ago against content hash df9ff9741a92, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

migrate-architecture 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 2d 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/migrate-architecture.md · 389 lines

How it starts

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

Architecture Migration

Plan and execute major architecture migrations with zero downtime, including monolith-to-microservices, database migrations, cloud migrations, and technology stack changes.

Purpose

Safely plan and execute complex architecture migrations with minimal risk, zero downtime, comprehensive rollback strategies, and data consistency guarantees through strategic migration patterns and phased execution.

Multi-Agent Coordination Strategy

Uses phased migration pattern with blue-green, canary, and strangler fig patterns coordinated across planning, execution, validation, and rollback phases.

Migration Architecture

``` ┌──────────────────────────────────────────────────┐ │ Migration Command Center │ │ (migration-orchestrator) │ └────────────┬─────────────────────────────────────┘ │ ┌────────┼────────┬────────┬────────┬─────────┐ ▼ ▼ ▼ ▼ ▼ ▼ Plan Build Test Deploy Monitor Rollback ```

Execution Flow

Phase 1: Migration Assessment (0-30 mins)

  1. migration-strategist - Assess migration complexity and strategy
  2. architecture-analyzer - Analyze current architecture
  3. dependency-mapper - Map all dependencies and integrations
  4. data-flow-analyzer - Analyze data flows and ownership
  5. risk-assessor - Identify migration risks
  6. stakeholder-impact-analyzer - Assess business impact

Phase 2: Migration Planning (30-75 mins)

  1. migration-pattern-selector - Select migration pattern (strangler, blue-green, etc.)
  2. phase-planner - Design phased migration approach
  3. rollback-strategist - Plan rollback procedures for each phase
  4. data-migration-planner - Design data migration strategy
  5. testing-strategist - Plan migration testing approach
  6. communication-planner - Stakeholder communication plan

Phase 3: Architecture Design (75-120 mins)

  1. target-architect - Design target architecture
  2. api-compatibility-designer - Design backward-compatible APIs
  3. data-schema-designer - Design target data schema
  4. integration-architect - Design integration patterns
  5. security-architect - Design security model for target
  6. observability-designer - Design monitoring and logging

Read the full file on GitHub · 389 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. 2d ago First seen · 389 lines · 0 tokens per session scan A df9ff9741a92

Subscribe to this mod's changes

migrate-architecture is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,129 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-05.