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.
/plugin marketplace add AleksandarBisevac/claude-plugins/plugin install auditWrote 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/aleksandarbisevac/claude-plugins/migrate)<a href="https://agentmods.dev/commands/aleksandarbisevac/claude-plugins/migrate"><img src="https://agentmods.dev/badge/commands/aleksandarbisevac/claude-plugins/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.1 | $0.00059 | $0.00478 |
| Opus 5 | $0.00030 | $0.00239 |
| Sonnet 5 | $0.00012 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
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 6d 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
/audit:migrate — the legacy spelling of /audit:layout sharded
This command still works. It is an alias, kept because transcripts, runbooks and older
documents already say it. It does one thing: what /audit:layout sharded does.
Do that, not something of your own. Read
${CLAUDE_PLUGIN_ROOT}/commands/layout.md and follow it with the direction fixed to sharded,
passing --dry-run / --renumber / --force through from $ARGUMENTS unchanged. There is no
second procedure here on purpose: two copies of a preflight is one copy and one lie.
Say the new name once, in the report — then get on with it. Something like "/audit:migrate
is the old name for /audit:layout sharded; both do this." One line, not a lecture, and never a
refusal to run.
Why it was renamed. migrate names a version upgrade — the tool moving forward, dragging old
state along. This is not that. Single-file and sharded are two equally current shapes of the same
schema: installing a newer plugin never makes a layout change due, and staying on single-file never
makes a manifest legacy. The old name said otherwise every time someone read it, and it named only
the one direction — /audit:layout also assembles shards back into a single file.
This alias will be removed in a future release. When it goes, /audit:migrate stops being a
command and a runbook that says it fails at that line. Anything written down — a project runbook, a
CI comment, a team wiki — is worth changing to /audit:layout sharded now, while both spellings
work.
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.
- 6d ago First seen · 31 lines · 59 tokens per session scan A b899a0416a1e
migrate is a command published in the GitHub repository AleksandarBisevac/claude-plugins (4 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 478 once invoked, about $0.0003 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
post
Post the current OCR review to a GitHub PR.
show
Display a past OCR review session.
history
List past OCR review sessions.
overlay-apply
Apply NIST 800-53 overlays (FedRAMP, DoD, Privacy, etc.) to existing baselines.
sdlc
Master orchestrator for the complete 5-phase SDLC pipeline. Runs all phases sequentially with approval gates and handoffs between each phase. Organizes artifacts into handoffs/, docs/, and projects/ directories.
pillar-guidance
Deep dive guidance on DORA's 5 pillars and implementation requirements.