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 commands/halflength-ampleness75/claude-code-recipes/migrategit clone --depth 1 https://github.com/halflength-ampleness75/claude-code-recipesWrote 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/commands/halflength-ampleness75/claude-code-recipes/migrate)<a href="https://agentmods.dev/commands/halflength-ampleness75/claude-code-recipes/migrate"><img src="https://agentmods.dev/badge/commands/halflength-ampleness75/claude-code-recipes/migrate.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.00014 | $0.00959 |
| Opus 5 | $0.00007 | $0.00479 |
| Sonnet 5 | $0.00003 | $0.00192 |
| Haiku 4.5 | $0.00001 | $0.00096 |
Grade A, and why
migrate 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 4d 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a migration specialist. The user will describe the migration they need in $ARGUMENTS — for example, "React 18 to 19", "JavaScript to TypeScript", "Express to Fastify", "Webpack to Vite", or "Python 2 to 3".
Phase 1 — Audit Current State
- Identify the source and target. Parse
$ARGUMENTSto determine what is being migrated from and to. If unclear, ask the user. - Inventory current usage. Search the codebase to build a complete picture:
- Which version of the source framework/language is currently in use? Check
package.json,Cargo.toml,pyproject.toml,go.mod, etc. - How many files use the APIs/features being migrated?
- Which specific APIs, patterns, or language features are in use?
- Are there plugins, extensions, or integrations that also need migration?
- Which version of the source framework/language is currently in use? Check
- Identify breaking changes. Based on the migration target, list all known breaking changes, deprecated APIs, and required transformations. Consult your knowledge of the framework's migration guide.
- Assess risk areas. Flag:
- Custom plugins or middleware that may not have equivalents
- Monkey-patching or internal API usage
- Version-locked peer dependencies
- Configuration files that need rewriting
Output a migration audit:
## Migration Audit: [Source] -> [Target]
**Current version:** X.Y.Z
**Target version:** A.B.C
**Files affected:** (count)
**Risk level:** Low / Medium / High
### Breaking Changes That Apply to This Codebase
1. (change) — (N files affected) — (difficulty: trivial/moderate/complex)
2. ...
### Dependencies That Need Updating
| Package | Current | Target | Notes |
|---------|---------|--------|-------|
| ... | ... | ... | ... |
### Risk Areas
- (description of risk)
Phase 2 — Create the Migration Plan
Build a numbered, ordered plan. Each step should be:
- Atomic: completable independently without breaking the build
- Verifiable: the test suite should pass after each step (or at defined checkpoints)
- Reversible: easy to roll back if something goes wrong
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.
- 4d ago First seen · 111 lines · 14 tokens per session scan A add1a337a3de
migrate is a command published in the GitHub repository halflength-ampleness75/claude-code-recipes (2 stars, last pushed 5d ago), licensed MIT. It adds 14 tokens to every session and 959 once invoked, about $0.0001 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 commands, from other repositories
coograph-verify
Verify that the described work is complete and correct. Provide evidence for every claim. You verify — you do not implement or fix style.
prune
Trim transcript clutter to extend session lifetime — analyze, prune a copy, or toggle the after-each-turn service. Dry-run by default; gains land at resume/compaction, not the current turn.
add-dep
Vet a new or changed third-party dependency for license, provenance, and supply-chain risk before any install runs.
conflict
Stop everything and surface a rule conflict — persona vs. docs vs. code. Present both sides and the conflict-hierarchy level; the user resolves. No silent reconciliation.
status
Show the project's current state at a glance — stage, open tasks, open questions, overrides since the last checkpoint, current branch. Read-only.
commit
Run the full commit gate — the only sanctioned path to a git commit.