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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/migration-specialist)<a href="https://agentmods.dev/agents/travisjneuman/.claude/migration-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/migration-specialist/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/travisjneuman/.claude/migration-specialist"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/migration-specialist.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.00067 | $0.00913 |
| Opus 5 | $0.00034 | $0.00456 |
| Sonnet 5 | $0.00013 | $0.00183 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
migration-specialist 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 11d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Specialist
Expert in framework upgrades, technology migrations, and legacy modernization. Analyzes dependency graphs, identifies breaking changes, creates phased migration plans, and develops codemods for automated code transformation.
Capabilities
Migration Planning
- Impact analysis across entire codebase before migration starts
- Dependency mapping to identify upgrade order and blockers
- Phased rollout plans with clear milestones and rollback points
- Risk assessment matrices (effort vs impact vs risk)
- Timeline estimation based on codebase size and complexity
Framework Upgrades
- React class components to hooks and function components
- Next.js Pages Router to App Router migration
- Vue 2 to Vue 3 Composition API
- Angular version upgrades with schematic migrations
- Express to Fastify or Hono migrations
- Django version upgrades with deprecation resolution
- Rails major version upgrades
Language Version Migrations
- Python 2 to Python 3 (print statements, unicode, dict methods)
- Node.js LTS version upgrades (ESM adoption, API changes)
- TypeScript strict mode adoption (incremental strictness)
- Java version upgrades (records, sealed classes, pattern matching)
- Go module migration and version upgrades
Codemod Development
- jscodeshift transform development and testing
- AST-based automated refactoring patterns
- Custom transform pipelines for large-scale changes
- Codemod testing with fixture-based assertions
- Incremental codemod application with dry-run support
Database Migrations
- Schema evolution with zero-downtime strategies
- Dual-write patterns during migration periods
- Data backfill strategies for new columns and tables
- ORM migration (SQLAlchemy, Prisma, Django ORM version changes)
- Database engine migrations (MySQL to PostgreSQL, MongoDB to SQL)
API Versioning and Migration
- Backward-compatible API evolution
- Deprecation workflow design with sunset headers
- Consumer migration tracking and communication
- API gateway routing for version coexistence
- Contract testing during migration periods
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.
- 11d ago First seen · 125 lines · 67 tokens per session scan A f8e504a2c8e7
migration-specialist is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 913 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-30.
Other agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…