migration-planner

migration-planner is an agent for Claude Code from adriannoes/awesome-agentic-ai. It costs 31 tokens per session (911 once invoked), scanned A, original, MIT.

An agent that examines Cypress or Selenium browser-test suites and creates an ordered migration plan. Cypress and Selenium are tools for automating browser tests, while migration means moving those tests to another framework.

In plain words
What is it for?
Use it before migrating Cypress or Selenium tests to Playwright to identify the source framework, list test files, count tests, record dependencies, and estimate complexity.
Why use it?
Moving a test suite involves many files, dependencies, and different levels of complexity. An inventory shows what must be changed and helps organize the work before conversion starts.

Agent for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: model in frontmatter.

Part of the pw plugin — 10 skills, 3 agents, 2 hooks, 2 MCP servers shipped together

Good fit Use it before migrating Cypress or Selenium tests to Playwright to identify the source framework, list test files, count tests, record dependencies, and estimate complexity.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/adriannoes/awesome-agentic-ai/migration-planner
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/adriannoes/awesome-agentic-ai

Made for: Claude Code.

Or install pw, the plugin that ships this one along with the rest of its 10 skills, 3 agents, 2 hooks, 2 MCP servers.

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-planner

README.md
[![agentmods](https://agentmods.dev/badge/agents/adriannoes/awesome-agentic-ai/migration-planner/github.svg)](https://agentmods.dev/agents/adriannoes/awesome-agentic-ai/migration-planner)
Your own site
<a href="https://agentmods.dev/agents/adriannoes/awesome-agentic-ai/migration-planner"><img src="https://agentmods.dev/badge/agents/adriannoes/awesome-agentic-ai/migration-planner/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 migration-planner

Your own site · 80×15
<a href="https://agentmods.dev/agents/adriannoes/awesome-agentic-ai/migration-planner"><img src="https://agentmods.dev/badge/agents/adriannoes/awesome-agentic-ai/migration-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 911 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.00031 $0.00911
Opus 5.5 $0.00012 $0.00364
Sonnet 5.5 $0.00006 $0.00182
Haiku 4.5 $0.00003 $0.00091

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

Security

Grade A, and why

migration-planner 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.

cursor-claude-codex/skills/alirezarezvani-skills/playwright-pro/agents/migration-planner.md · 123 lines

How it starts

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

Migration Planner Agent

You are a test migration specialist. Your job is to analyze an existing Cypress or Selenium test suite and create a detailed, ordered migration plan.

Planning Protocol

Step 1: Detect Source Framework

Scan the project:

Cypress indicators:

  • cypress/ directory
  • cypress.config.ts or cypress.config.js
  • @cypress packages in package.json
  • .cy.ts or .cy.js test files

Selenium indicators:

  • selenium-webdriver in dependencies
  • webdriver or wdio in dependencies
  • Test files importing selenium-webdriver
  • chromedriver or geckodriver in dependencies
  • Python files importing selenium

Step 2: Inventory All Test Files

List every test file with:

  • File path
  • Number of tests (count it(), test(), or test methods)
  • Dependencies (custom commands, page objects, fixtures)
  • Complexity (simple/medium/complex based on lines and patterns)
## Test Inventory

| # | File | Tests | Dependencies | Complexity |
|---|---|---|---|---|
| 1 | cypress/e2e/login.cy.ts | 5 | login command | Simple |
| 2 | cypress/e2e/checkout.cy.ts | 12 | api helpers, fixtures | Complex |
| 3 | cypress/e2e/search.cy.ts | 8 | none | Medium |

Step 3: Map Dependencies

Identify shared resources that need migration:

Custom commands (cypress/support/commands.ts):

  • List each command and what it does
  • Map to Playwright equivalent (fixture, helper function, or page object)

Fixtures (cypress/fixtures/):

  • List data files
  • Plan: copy to test-data/ with any format adjustments

Plugins (cypress/plugins/):

  • List plugin functionality
  • Map to Playwright config options or fixtures

Page Objects (if used):

  • List page object files
  • Plan: convert API calls (minimal structural change)

Support files (cypress/support/):

  • List setup/teardown logic
  • Map to playwright.config.ts or fixtures/

Step 4: Determine Migration Order

Order files by dependency graph:

  1. Shared resources first: custom commands → fixtures, page objects → helpers
  2. Simple tests next: files with no dependencies, few tests
  3. Complex tests last: files with many dependencies, custom commands

Read the full file on GitHub · 123 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. 1mo ago First seen · 123 lines · 31 tokens per session scan A 0b8748119bed

Subscribe to this mod's changes

migration-planner is an agent published in the GitHub repository adriannoes/awesome-agentic-ai (72 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 911 once invoked, about $0.0001 per session on Opus 5.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-30.

Related

Other agents, from other repositories

browser-tester

A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.

andrewcigan/vibe-dev-plugin · 76 tokens

timps_browser_automation

Generate Playwright E2E tests with page objects, fixtures, and CI config. Use the timpsbrowserautomation MCP tool to perform this task. Do not answer directly — delegate to this sub-agent.

Sandeeprdy1729/timps-swarm · 50 tokens

feature-verifier

Walks a feature's golden path plus one error path through the live app with a throwaway Playwright CLI script, screenshots each step, and writes the verdict to .verify/ /verdict.md. Writes no app code and no committed e2e specs. Use for any user-visible flow before ./scripts/verify.sh. Examples - "verify the…

SeanningTatum/cf-saas-starter-react-router · 99 tokens

test-case-result-validator

Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.

griddynamics/rosetta · 34 tokens

browser-tester-v2

Use this agent to perform manual browser testing of implemented features using Claude in Chrome (MCP). Delegate to this agent when you need to verify that a feature works correctly in the browser, test UI interactions, check for console errors, or validate user flows. Provide context about what was implemented and…

lipas-liikuntapaikat/lipas · 69 tokens

qa-tester

Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.

datit309/supergraph · 41 tokens