A guided command for carrying out a multi-step code migration, such as replacing a deprecated API with a newer one. It inventories affected code, plans reviewable steps, and verifies each stage.

Use it to migrate deprecated symbols or patterns, with a clean-worktree check, occurrence inventory, staged execution, verification, and an Unreleased changelog entry.

It makes large changes easier to review and limits the chance of silently missing usages or breaking tests. The workflow stops at failures and checks tests, types, and project linting.

migrate — Command for Claude Code by JuliusBrussee/caveman-code

Install

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.

Clone the repo

git clone --depth 1 https://github.com/JuliusBrussee/caveman-code

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/juliusbrussee/caveman-code/migrate/github.svg)](https://agentmods.dev/commands/juliusbrussee/caveman-code/migrate)

Your own site

<a href="https://agentmods.dev/commands/juliusbrussee/caveman-code/migrate"><img src="https://agentmods.dev/badge/commands/juliusbrussee/caveman-code/migrate/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/juliusbrussee/caveman-code/migrate"><img src="https://agentmods.dev/badge/commands/juliusbrussee/caveman-code/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 307 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00013	$0.00307
Opus 5.5	$0.00005	$0.00123
Sonnet 5.5	$0.00003	$0.00061
Haiku 4.5	$0.00001	$0.00031

Measured 2mo ago against content hash e5082f7e560b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 2mo 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.

packages/coding-agent/commands/migrate.md · 36 lines

What it actually says

Execute a code migration named $1 (target: ${2:-latest}).

Generic migration playbook (apply iff the named migration matches one of these shapes; otherwise plan first):

Snapshot. Confirm the working tree is clean — abort if not.
Inventory. Search for every occurrence of the deprecated symbol / pattern. Report counts grouped by file. Pause for user approval.
Plan. List the migration in 3–7 numbered steps. Each step must be:
- Reviewable in isolation.
- Independently testable (or explicitly marked "no test possible").
Execute step-by-step. After each step:
- Run the affected tests.
- Run the type-checker.
- Stop on the first failure and ask the user before proceeding.
Verify. Run the full test suite and any project-specific lints.
Document. Append a CHANGELOG entry under ## Unreleased.

Hard rules:

Never combine multiple steps into one commit.
Never disable tests "temporarily" — fix or revert.
Pin third-party version bumps to exact versions during migration; relax the pin in a follow-up PR.

Changes

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.

2mo ago First seen · 36 lines · 13 tokens per session scan A e5082f7e560b

Subscribe to this mod's changes

migrate is a command published in the GitHub repository JuliusBrussee/caveman-code (947 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 307 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-08-30.

Planning

migrate next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
migrateJuliusBrussee/caveman-code	Command	947	2mo ago	MIT	A	13	Claude Code
checklistgithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	yesterday	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	yesterday	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	yesterday	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	yesterday	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	yesterday	MIT	A	14	Claude Code