A repository migration workflow that moves instruction content from CLAUDE.md into AGENTS.md while keeping a small compatibility reference for Claude Code. It plans changes first and requires approval before writing them.

It is for planning and applying a repository-wide move of agent instructions, while checking file locations, size limits, and references that must remain compatible.

It avoids maintaining the same coding-agent instructions in multiple files and lets tools share one main source of guidance.

migrate — Skill for Claude Code by melodic-software

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add melodic-software/claude-code-plugins

Claude Code

/plugin install instruction-placement

Made for: Claude Code.

Or install instruction-placement, the plugin that ships this one along with the rest of its 3 skills.

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/skills/melodic-software/claude-code-plugins/migrate/github.svg)](https://agentmods.dev/skills/melodic-software/claude-code-plugins/migrate)

Your own site

<a href="https://agentmods.dev/skills/melodic-software/claude-code-plugins/migrate"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/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/skills/melodic-software/claude-code-plugins/migrate"><img src="https://agentmods.dev/badge/skills/melodic-software/claude-code-plugins/migrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 127 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 9,033 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.00127	$0.09033
Opus 5.5	$0.00051	$0.03613
Sonnet 5.5	$0.00025	$0.01807
Haiku 4.5	$0.00013	$0.00903

Measured 3d ago against content hash 2a618dac614f, 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 3d ago.

The scan reads SKILL.md. This mod also ships 6 executable files (scripts/cutover-check.sh, scripts/cutover-check.test.sh, scripts/plan-migration.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/instruction-placement/skills/migrate/SKILL.md · 500 lines

How it starts

The opening of the file, as written. The whole thing — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Arguments. [plan|apply|cutover-check|remove-shims] [path ...]. Default: plan the repository at the current root

Migrate a repository to AGENTS.md

Purpose

One tool-agnostic instruction source per repository, small enough to load every session, readable by Codex, Cursor and every other agent that reads AGENTS.md, and still reaching Claude Code in the sessions that cannot read AGENTS.md directly.

Two mutating skills live in this plugin. /instruction-placement:realign executes findings a sibling audit produced, one at a time. This one owns a different unit of work: a repository's move from CLAUDE.md to AGENTS.md as the content home, which is a decision about a whole instruction layer rather than a list of findings. It gates every write on the operator just as realign does.

A migration run never removes a shim. Removal is a cutover with upstream conditions of its own, and it is the cutover-check and remove-shims arguments below. Never delete a CLAUDE.md shim during plan or apply, however unnecessary it looks.

Invocation mode

disable-model-invocation: false, the fleet default. No exception class in the invocation-mode rubric fits: this is not a setup skill (class ii), not maintainer-only (class iii), and not class (i) either, since the human already decides every write at the gate below rather than deciding the timing of an unattended mutation. It is also a chain target: /harness-memory:audit's N1 fix route and this plugin's own setup remediation both point a repository here, and the invocation-reach invariant makes a true skill unreachable from another skill.

The target shape

The root CLAUDE.md is exactly the one line @AGENTS.md. No heading, no comment, no other text.
Every directory with a Claude-audience nested AGENTS.md has a sibling CLAUDE.md that is exactly @AGENTS.md.
AGENTS.md carries the content. CLAUDE.md carries nothing but the import.
.cursor/, .codex/ and .github/ belong to those tools. Their instruction files are never given a Claude shim and never merged into AGENTS.md.

Read the full file on GitHub · 500 lines

Files

What ships with it

10 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

3d ago Changed 2a618dac614f
6d ago Changed · +8 lines 1549701b624b
7d ago Changed · +4 lines cf20aa74378f
12d ago Changed · +9 lines b2827661342e
15d ago Changed · +2 lines 4ecfa558b976
17d ago Changed · +37 lines 1d9cbab2145a
18d ago Changed · +10 lines ea539efb556f
19d ago Changed · +1 lines 2f7b753a4327
20d ago Changed · +2 lines df0fb51b6c11
21d ago First seen · 427 lines · 127 tokens per session scan A 2c6724dfdd34

Subscribe to this mod's changes

migrate is a skill published in the GitHub repository melodic-software/claude-code-plugins (26 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 9,033 once invoked, about $0.0005 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-21.

Building agents Claude Code agents ai-tools marketplace mcp plugins

parallel-orchestrator

Manage parallel Claude Code workstreams using git worktrees. Use when: splitting large tasks across multiple workers, coordinating parallel development, monitoring worker progress, integrating completed work, analyzing work item documents (code reviews, issue lists). Triggers: parallel, orchestrator, worktrees…

jimmc414/claude-code-plugin-marketplace · 78 tokens

parallel-worker

Execute focused implementation tasks in a parallel workflow. Use when: working on assigned files in a worktree, making checkpoint commits, signaling dependencies or blockers, completing orchestrator-assigned tasks. Triggers: worker, checkpoint, worktree, assigned scope, commit prefix, parallel task.

jimmc414/claude-code-plugin-marketplace · 59 tokens

migrate