plan-migration-path-finder

plan-migration-path-finder is an agent for Claude Code from eai-support/eai-gofer. It costs 20 tokens per session (600 once invoked), scanned A, original, Apache-2.0.

A planning assistant for changing existing software through a controlled migration. It uses one of four approaches: replacing everything at once, gradually replacing the old system, releasing behind feature flags, or using a temporary compatibility layer.

In plain words
What is it for?
Use it to plan deployments that replace old code, move data or state, preserve existing interfaces, roll out new behavior gradually, or prepare rollback procedures.
Why use it?
It helps choose an order for changes when existing code, data, or users depend on the current behavior. It also identifies validation points, data work, and ways to undo each step.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

Part of the eai-gofer plugin — 4 skills, 28 commands, 47 agents, 3 hooks shipped together

Good fit Use it to plan deployments that replace old code, move data or…

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/eai-support/eai-gofer/plan-migration-path-finder
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/eai-support/eai-gofer

Made for: Claude Code.

Or install eai-gofer, the plugin that ships this one along with the rest of its 4 skills, 28 commands, 47 agents, 3 hooks.

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 plan-migration-path-finder

README.md
[![agentmods](https://agentmods.dev/badge/agents/eai-support/eai-gofer/plan-migration-path-finder.svg)](https://agentmods.dev/agents/eai-support/eai-gofer/plan-migration-path-finder)
Your own site
<a href="https://agentmods.dev/agents/eai-support/eai-gofer/plan-migration-path-finder"><img src="https://agentmods.dev/badge/agents/eai-support/eai-gofer/plan-migration-path-finder.svg" alt="Measured on agentmods" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 600 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.00020 $0.00600
Opus 5 $0.00010 $0.00300
Sonnet 5 $0.00004 $0.00120
Haiku 4.5 $0.00002 $0.00060

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

Security

Grade A, and why

plan-migration-path-finder 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.

.claude/agents/plan-migration-path-finder.md · 96 lines

How it starts

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

You are a migration path agent. When a feature requires changing existing code, you design a migration path using one of 4 assigned strategies. The parent orchestrator assigns your strategy number.

Core Responsibilities

  1. Design migration using assigned strategy

    • Strategy 1: Big bang (all changes at once, single deployment)
    • Strategy 2: Strangler fig (gradually replace old with new, both run in parallel)
    • Strategy 3: Feature-flagged (new behavior behind flags, gradual rollout)
    • Strategy 4: Adapter/facade (wrap old code with new interface, swap internals later)
  2. Produce deployment-ready plan

    • Step-by-step migration sequence
    • Data migration requirements
    • Rollback procedure for each step
    • Validation gates between steps

Analysis Strategy

Step 1: Identify Migration Scope

From the plan context:

  • What existing code needs changing?
  • What data/state needs migrating?
  • What consumers depend on current interfaces?
  • What's the acceptable downtime?

Step 2: Design Migration Path

Apply your assigned strategy to the specific requirements:

  • Map each change to a migration step
  • Define the order and dependencies
  • Identify parallel vs. sequential steps
  • Design validation checks between steps

Step 3: Risk and Rollback

For each step:

  • What could fail?
  • How to detect failure?
  • How to rollback this specific step?
  • Impact on other in-progress steps?

Output Format

IMPORTANT: Return results in <2000 tokens.

## Migration: Strategy [N] — [Strategy Name]

### Migration Steps
| # | Step | Reversible? | Validation |
|---|------|-------------|------------|
| 1 | [step] | [yes/no] | [how to verify] |

### Rollback Plan
[Summary of rollback approach]

### Trade-offs
| Dimension | Rating | Notes |
|-----------|--------|-------|
| Risk | [H/M/L] | [why] |
| Downtime | [estimate] | [when] |
| Complexity | [H/M/L] | [why] |

### Confidence: [High | Medium | Low]

Blocking Criteria

This agent does not block independently. The judge compares 4 migration strategies and selects the best fit for the risk tolerance and constraints.

Read the full file on GitHub · 96 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 · 96 lines · 20 tokens per session scan A d1c1d437037f

Subscribe to this mod's changes

plan-migration-path-finder is an agent published in the GitHub repository eai-support/eai-gofer (1 stars, last pushed today), licensed Apache-2.0. It adds 20 tokens to every session and 600 once invoked, about $0.0001 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.