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.
git clone --depth 1 https://github.com/adriannoes/awesome-agentic-aiWrote 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.
[](https://agentmods.dev/agents/adriannoes/awesome-agentic-ai/migration-planner)<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.
<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>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00031 | $0.00911 |
| Opus 5 | $0.00015 | $0.00456 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
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 9d 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.
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/directorycypress.config.tsorcypress.config.js@cypresspackages inpackage.json.cy.tsor.cy.jstest files
Selenium indicators:
selenium-webdriverin dependencieswebdriverorwdioin dependencies- Test files importing
selenium-webdriver chromedriverorgeckodriverin 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.tsorfixtures/
Step 4: Determine Migration Order
Order files by dependency graph:
- Shared resources first: custom commands → fixtures, page objects → helpers
- Simple tests next: files with no dependencies, few tests
- Complex tests last: files with many dependencies, custom commands
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.
- 9d ago First seen · 123 lines · 31 tokens per session scan A 0b8748119bed
migration-planner is an agent published in the GitHub repository adriannoes/awesome-agentic-ai (57 stars, last pushed 11d ago), licensed MIT. It adds 31 tokens to every session and 911 once invoked, about $0.0002 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-30.
Other agents, from other repositories
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
forge-visual-verifier
Perceptual gate for spec [visual] acceptance criteria. Drives Playwright MCP (navigate + takescreenshot + evaluate), compares the resulting image against a saved baseline via an LLM-vision step, and reports pass|fail|blocked per AC. Invoked after all task-level structural checks pass and before FORGECOMPLETE is…
qa-chrome
Visual audit and browser testing via Chrome. Use to test web pages, verify rendering, debug the console, or automate browser interactions. Requires the --chrome flag.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
ux-evaluator
Use this agent for read-only UX evaluation of test-runner driver artifacts (Playwright AX-tree snapshots, screenshots, console output). Applies the 4-check UX rubric (onboarding-step-count ≤7, axe-violations critical/serious, console-errors visible to user, Apple-Liquid-Glass .glassEffect() conformance on SwiftUI 26+)…
playwright-e2e
Playwright E2E testing specialist. Use for writing, reviewing, debugging, and optimizing Playwright tests. Proactively use when working with test files (.spec.ts), page objects, or test helpers.