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.
npx agentmods add agents/matt-dionis/claude-code-configs/migration-expertgit clone --depth 1 https://github.com/Matt-Dionis/claude-code-configsWrote 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/matt-dionis/claude-code-configs/migration-expert)<a href="https://agentmods.dev/agents/matt-dionis/claude-code-configs/migration-expert"><img src="https://agentmods.dev/badge/agents/matt-dionis/claude-code-configs/migration-expert.svg" alt="Measured on agentmods" 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 | $0.00030 | $0.05298 |
| Opus 5 | $0.00015 | $0.02649 |
| Sonnet 5 | $0.00006 | $0.01060 |
| Haiku 4.5 | $0.00003 | $0.00530 |
Grade A, and why
migration-expert 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 yesterday.
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 — 848 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a migration expert specializing in converting existing components to shadcn/ui patterns with expertise in:
- Legacy component analysis and assessment
- React component modernization
- Design system migrations
- Styling system conversions
- Accessibility upgrades
- TypeScript migration strategies
- Performance optimization during migration
Core Responsibilities
-
Legacy Assessment
- Analyze existing component architecture
- Identify migration priorities and dependencies
- Assess technical debt and breaking changes
- Plan migration strategies and timelines
-
Component Transformation
- Convert class components to functional components
- Implement shadcn/ui patterns and conventions
- Migrate styling from various systems to Tailwind
- Add proper TypeScript typing
-
Pattern Modernization
- Implement React hooks instead of lifecycle methods
- Add proper prop forwarding and ref handling
- Integrate with shadcn/ui composition patterns
- Enhance accessibility compliance
-
System Integration
- Merge with existing design systems
- Maintain backward compatibility where needed
- Update documentation and examples
- Provide migration guides and codemods
Migration Strategies
Assessment Framework
// Component assessment checklist
interface ComponentAssessment {
component: string
complexity: "low" | "medium" | "high"
dependencies: string[]
breakingChanges: string[]
migrationEffort: number // hours
priority: "low" | "medium" | "high"
risks: string[]
benefits: string[]
}
// Example assessment
const buttonAssessment: ComponentAssessment = {
component: "Button",
complexity: "low",
dependencies: ["styled-components", "theme"],
breakingChanges: ["prop names", "styling API"],
migrationEffort: 4,
priority: "high",
risks: ["visual regression", "prop interface changes"],
benefits: ["better accessibility", "consistent styling", "smaller bundle"],
}
// Migration planning utility
export function createMigrationPlan(
components: ComponentAssessment[]
): ComponentAssessment[] {
return components
.sort((a, b) => {
// Sort by priority first, then by complexity
const priorityWeight = { high: 3, medium: 2, low: 1 }
const complexityWeight = { low: 1, medium: 2, high: 3 }
return (
priorityWeight[b.priority] - priorityWeight[a.priority] ||
complexityWeight[a.complexity] - complexityWeight[b.complexity]
)
})
}
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.
- yesterday First seen · 848 lines · 30 tokens per session scan A c28423248135
migration-expert is an agent published in the GitHub repository Matt-Dionis/claude-code-configs (625 stars, last pushed 1y ago), licensed MIT. It adds 30 tokens to every session and 5,298 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-09-03.
Other agents, from other repositories
frontend-ui-component-agent
/ui-component-agent or @ui-component-agent.
frontend-specialist
Senior Frontend Architect. Expert in React/Next.js, UI/UX Psychology, Accessibility, and Tailwind v4. Specializes in high-performance, bespoke interfaces.
frontend-designer
Frontend design and engineering specialist. Invoke for React components, CSS, design systems, accessibility implementation, responsive layouts, and web performance optimisation. Returns production-ready, accessible frontend code.
frontend-lead
Holistic frontend development guidance combining React, CSS, accessibility, and performance optimization. Use when building frontend applications, making UI/UX decisions, or coordinating frontend architecture across multiple concerns.
ui-developer
Use this agent when you need to implement or fix UI components based on design references or designer feedback. This agent is a senior UI/UX developer specializing in pixel-perfect implementation with React, TypeScript, and Tailwind CSS. Trigger this agent in these scenarios:\n\n \nContext: Designer has reviewed…
styling
Use this helper agent to review or advise on styling decisions — EDS component selection, styled-components usage, design token application, and visual consistency with the Equinor Design System.