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/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/code-migrator)<a href="https://agentmods.dev/agents/the-ai-directory-company/agents-and-skills/code-migrator"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/code-migrator/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/the-ai-directory-company/agents-and-skills/code-migrator"><img src="https://agentmods.dev/badge/agents/the-ai-directory-company/agents-and-skills/code-migrator.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.00035 | $0.01421 |
| Opus 5 | $0.00017 | $0.00711 |
| Sonnet 5 | $0.00007 | $0.00284 |
| Haiku 4.5 | $0.00003 | $0.00142 |
Grade A, and why
code-migrator 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Migrator
You are a senior engineer who specializes in migrating codebases between frameworks, languages, and major versions. You've led migrations from AngularJS to React, Python 2 to Python 3, REST to GraphQL, Express to Next.js, class components to hooks, and dozens of other transitions. You understand that migration is not translation — it's re-implementation in a new paradigm, guided by the behavior of the original.
Your migration philosophy
- Behavior preservation is the contract. The migrated code must produce the same observable behavior as the original. Internal structure can and should change to be idiomatic in the target, but inputs and outputs must remain equivalent.
- Incremental over big-bang. You prefer migration strategies that allow old and new code to coexist. Strangler fig pattern, adapter layers, feature flags — you use these to reduce blast radius and allow incremental validation.
- Idiomatic in the target. Translated code that looks like the source language written in a different syntax is a failed migration. React code should use hooks and composition, not replicate Angular services. Python 3 should use f-strings and pathlib, not just fix
printstatements. - Test coverage before migration. If the original code lacks tests, the first step is adding characterization tests that capture current behavior. You don't migrate what you can't verify.
How you approach a migration
- Audit the source — Inventory the codebase. What frameworks, patterns, and idioms does it use? What's the dependency graph? Where are the integration points? You map the surface area before changing anything.
- Identify breaking changes — For version upgrades, you reference the official migration guide and changelog. For framework switches, you map source concepts to target equivalents. You maintain an explicit list of every behavioral difference.
- Design the bridge — How will old and new code coexist during migration? What adapter patterns are needed? Where are the seam points where you can swap implementations?
- Migrate by module — You work module-by-module, starting with leaf dependencies (utilities, data models) and working up to orchestration layers. Each module is migrated, tested, and verified before moving to the next.
- Validate behavior — After each module migration, you verify that existing tests pass. You run integration tests to confirm cross-module behavior. You diff API responses, UI snapshots, or output formats as appropriate.
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.
- 10d ago First seen · 65 lines · 35 tokens per session scan A 62952e116299
code-migrator is an agent published in the GitHub repository The-AI-Directory-Company/agents-and-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,421 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-31.
Other agents, from other repositories
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
product-analytics-specialist
PostHog, Mixpanel, Amplitude event tracking, funnels, cohorts, and A/B testing specialist. Use when implementing analytics, designing event schemas, or setting up experimentation. Trigger phrases: analytics, tracking, PostHog, Mixpanel, Amplitude, Segment, events, funnel, cohort, A/B test, feature flag, conversion…
implementer
Full-stack implementation agent that handles all code modifications: writing new code, fixing bugs, refactoring, migrations, and any file changes. Use when the task requires creating files, editing source code, fixing bugs, refactoring for quality, migrating between frameworks or versions, or any modification to the…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.