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 Abilityai/abilities/plugin install agent-devWrote 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/skills/abilityai/abilities/agent-fleet-migrate)<a href="https://agentmods.dev/skills/abilityai/abilities/agent-fleet-migrate"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/agent-fleet-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.
<a href="https://agentmods.dev/skills/abilityai/abilities/agent-fleet-migrate"><img src="https://agentmods.dev/badge/skills/abilityai/abilities/agent-fleet-migrate.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.00110 | $0.05006 |
| Opus 5.5 | $0.00044 | $0.02002 |
| Sonnet 5.5 | $0.00022 | $0.01001 |
| Haiku 4.5 | $0.00011 | $0.00501 |
Grade A, and why
agent-fleet-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 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.
How it starts
The opening of the file, as written. The whole thing — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Fleet Migrate
ℹ️ First, set expectations: before anything else, print one short line with this skill's version and its most recent change — the top entry of
metadata.changelogabove — e.g.agent-fleet-migrate vX.Y — recent: <summary>. Then proceed.
Execute the work order that /agent-dev:agent-fleet-analysis produces. The analysis is the diagnose half; this skill is the execute half — the same relationship as create-agent:review → create-agent:adjust, one level up.
Three properties are non-negotiable:
- Non-destructive. Source agents are never mutated — not even "safe" fixes. All writes land in the target workspace; a run is reversible by deleting a folder. The run proves this at the end (Step 7).
- Composition, not duplication. This skill owns exactly three things: copy semantics, per-paradigm logic extraction, and the fleet-level before/after report. Every other stage is a named skill invocation (see the composition table). This file must contain no inline restatement of any composed skill's checks or templates — a restated rubric line is future drift. Gaps found in a composed skill get fixed in that skill.
- Honest gates. An agent is reported "migrated" only after the review gate passes and the re-score clears the bar (Step 4d). Failures are reported as failures with named findings — never rounded up. A gate FAIL is a blocker, not an advisory.
Composition table
| Stage | Invoke |
|---|---|
| Work order (missing or stale) | /agent-dev:agent-fleet-analysis |
| Scaffold target shape (non-Claude-Code paradigms) | /create-agent:custom |
| Extracted capabilities → skills | /agent-dev:create-playbook |
| Gap fixes on the copies | /create-agent:adjust (composes the review itself) |
| Memory / hub / canon wiring | /agent-dev:add-memory · /agent-dev:add-orchestrator · /agent-dev:add-canon — driven by the work order's upgrade_paths, which already names the skill per agent |
| Verification gate | /create-agent:review per migrated copy |
| Numeric before/after | /agent-dev:agent-fleet-analysis re-run on the target workspace |
| Deploy handoff (gated) | A GitHub repo per migrated agent, then /trinity:onboard per agent (deploys from the repo), or mcp__trinity__deploy_system naming each member github:Org/repo |
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 Changed · +1 lines 22fada0cb10a
- 1mo ago First seen · 290 lines · 110 tokens per session scan A 63d2de33461f
agent-fleet-migrate is a skill published in the GitHub repository Abilityai/abilities (12 stars, last pushed 3d ago), licensed MIT. It adds 110 tokens to every session and 5,006 once invoked, about $0.0004 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.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…