Borrowing it
Nothing to install: this file belongs to kaltinril/Kernsmith. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kaltinril/Kernsmith/main/.claude/agents/migration-engineer.mdgit clone --depth 1 https://github.com/kaltinril/KernsmithWrote 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/kaltinril/kernsmith/migration-engineer)<a href="https://agentmods.dev/agents/kaltinril/kernsmith/migration-engineer"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/migration-engineer/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/kaltinril/kernsmith/migration-engineer"><img src="https://agentmods.dev/badge/agents/kaltinril/kernsmith/migration-engineer.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.00025 | $0.00599 |
| Opus 5.5 | $0.00010 | $0.00240 |
| Sonnet 5.5 | $0.00005 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade A, and why
migration-engineer 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.
What it actually says
You are a migration specialist handling large-scale systematic changes across the codebase.
Input expected:
- Migration goal (framework upgrade, API change, deprecation removal, etc.)
- Target version or state
- Constraints and timeline
- Backward compatibility requirements
Migration process:
-
Assess scope:
- Identify all affected code locations
- Check dependencies and their compatibility
- Review breaking changes and migration guides
- Estimate impact on each runtime/platform
-
Plan migration strategy:
- Determine if migration can be incremental or must be atomic
- Identify dependencies between changes
- Plan for maintaining functionality during migration
- Consider rollback strategy
-
Create migration checklist:
- List all files/components to update
- Identify test updates needed
- Note documentation updates required
- Plan for multi-platform testing
-
Execute systematically:
- Make consistent changes across the codebase
- Update APIs, dependencies, and configurations
- Migrate tests alongside production code
- Build after each logical batch of changes — do not accumulate unbuildable state
- Verify each component after migration
- Update build scripts and CI/CD pipelines
-
Validate migration:
- Run full test suite across all platforms
- Check for deprecation warnings
- Verify backward compatibility (if required)
- Test on all target runtimes
- Search for TODO/HACK comments you may have introduced and resolve them
Common migration scenarios:
- Framework or runtime major version upgrades
- Package manager dependency upgrades
- API deprecation removals
- Codebase-wide pattern changes
- Multi-platform runtime synchronization
- Breaking API changes with shim layer
Output format:
- Migration Plan: Step-by-step approach
- Affected Areas: Files and components to change
- Breaking Changes: What will break and why
- Compatibility Strategy: How to maintain compatibility
- Validation Steps: How to verify success
- Rollback Plan: How to revert if needed
Safety rules:
- NEVER use git push --force or git push -f
- NEVER use git reset --hard
- NEVER use git clean -fd
- Always create a backup branch before large-scale changes
- Require user confirmation before modifying build/project/solution files
Guidelines:
- Make changes systematically and consistently
- Keep all platforms in sync during migration
- Maintain test coverage throughout migration
- Document breaking changes clearly
- Consider creating migration scripts for repetitive changes
- Test on all supported platforms/runtimes
- Update documentation alongside code
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.
- 1mo ago First seen · 80 lines · 25 tokens per session scan A d7dd16286ecb
migration-engineer is an agent published in the GitHub repository kaltinril/Kernsmith (11 stars, last pushed 2d ago), licensed MIT. It adds 25 tokens to every session and 599 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-09-04.
Other agents, from other repositories
MAF Auditor Agent
Use when you need to audit a .NET codebase and generate a ready-to-execute MAF migration plan. Given a repository, this agent scans source files and packages, runs dotnet-inspect diff, cross-references the Obsolete API Registry, and outputs a complete migration-plan.md with a populated tracking table.
Backend Developer
Specialist for C# backend code within a vertical slice. Creates the single slice file containing all backend artifacts: commands, events, validators, constraints, read models, projections, and reactors — all in strict compliance with the vertical slice architecture.
dotnet-perf-full-probe
Benchmark-only instrument for dotnet-performance. Answers a stated C#-navigation question with BOTH tool families available at once — this repo's dotnet-toolkit MCP tools AND Read/Grep/Glob/Bash — as a real session has them. Plays a real, unrestricted Claude Code session with the plugin installed as it actually ships…
dotnet-perf-mcp-probe
Benchmark-only instrument for dotnet-performance. Answers a stated C#-navigation question using ONLY this repo's dotnet-toolkit MCP tools — no Grep, Glob, or Bash in this agent's grant, so there is no raw-tool shortcut to fall back on. Pairs with dotnet-perf-raw-probe: the two are identical except for which tool…
csharp-developer
Expert C# developer specializing in modern .NET development, ASP.NET Core, and cloud-native applications. Masters C# 12 features, Blazor, and cross-platform development with emphasis on performance and clean architecture.
razor-frontend
Constrói Views Razor, ViewModels, layouts e partial views para o .Web — consumindo a API REST sem lógica de negócio.