agent-migration-plan

agent-migration-plan is a skill for Claude Code, Codex from ruvnet/ruflo. It costs 18 tokens per session (4,679 once invoked), scanned A, original, MIT.

A planning skill for moving command-based automation to an agent-based system. It maps existing commands to agents and examines compatibility and rollout needs.

In plain words
What is it for?
Use it to inspect existing command files, plan their agent equivalents, analyse compatibility, and coordinate a staged migration.
Why use it?
It provides a structured way to understand the current command setup before changing how the system is organised.

Skill for Claude CodeCodex

Part of the claude-flow plugin — 134 skills, 52 commands, 11 agents, 4 hooks shipped together

About the project

Ruflo is an execution and coordination layer for Claude Code and Codex that equips AI coding agents with tools, memory, control loops, sandboxes, and collaboration mechanisms. Developers use it to organize specialized agents into swarms, coordinate workflows, retain knowledge across sessions, and communicate across machines. The catalogue entries are Ruflo’s skills, commands, agents, hooks, and plugin components.

ruvnet/ruflo · 70,498 stars · on GitHub · cognitum.one

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.

agentmods
npx agentmods add skills/ruvnet/ruflo/agent-migration-plan
Any agent
npx skills add ruvnet/ruflo --skill agent-migration-plan
Clone the repo
git clone --depth 1 https://github.com/ruvnet/ruflo

Made for: Claude Code, Codex.

Or install claude-flow, the plugin that ships this one along with the rest of its 134 skills, 52 commands, 11 agents, 4 hooks.

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.

agentmods badge for agent-migration-plan

README.md
[![agentmods](https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-migration-plan.svg)](https://agentmods.dev/skills/ruvnet/ruflo/agent-migration-plan)
Your own site
<a href="https://agentmods.dev/skills/ruvnet/ruflo/agent-migration-plan"><img src="https://agentmods.dev/badge/skills/ruvnet/ruflo/agent-migration-plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,679 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.04679
Opus 5 $0.00009 $0.02339
Sonnet 5 $0.00004 $0.00936
Haiku 4.5 $0.00002 $0.00468

Measured 6d ago against content hash 8443b2abf465, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

agent-migration-plan 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.

Origin

Copies of this mod

3 near-identical copies found in the catalogue:

.agents/skills/agent-migration-plan/SKILL.md · 751 lines

How it starts

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


name: migration-planner type: planning color: red description: Comprehensive migration plan for converting commands to agent-based system capabilities:

  • migration-planning
  • system-transformation
  • agent-mapping
  • compatibility-analysis
  • rollout-coordination priority: medium hooks: pre: | echo "📋 Agent System Migration Planner activated" echo "🔄 Analyzing current command structure for migration"

    Check existing command structure

    if [ -d ".claude$commands" ]; then echo "📁 Found existing command directory - will map to agents" find .claude$commands -name "*.md" | wc -l | xargs echo "Commands to migrate:" fi post: | echo "✅ Migration planning completed" echo "📊 Agent mapping strategy defined" echo "🚀 Ready for systematic agent system rollout"

Claude Flow Commands to Agent System Migration Plan

Overview

This document provides a comprehensive migration plan to convert existing .claude$commands to the new agent-based system. Each command is mapped to an equivalent agent with defined roles, responsibilities, capabilities, and tool access restrictions.

Agent Definition Format

Each agent uses YAML frontmatter with the following structure:

---
role: agent-type
name: Agent Display Name
responsibilities:
  - Primary responsibility
  - Secondary responsibility
capabilities:
  - capability-1
  - capability-2
tools:
  allowed:
    - tool-name
  restricted:
    - restricted-tool
triggers:
  - pattern: "regex pattern"
    priority: high|medium|low
  - keyword: "activation keyword"
---

Migration Categories

1. Coordination Agents

Swarm Initializer Agent

Command: .claude$commands$coordination$init.md

---
role: coordinator
name: Swarm Initializer
responsibilities:
  - Initialize agent swarms with optimal topology
  - Configure distributed coordination systems
  - Set up inter-agent communication channels
capabilities:
  - swarm-initialization
  - topology-optimization
  - resource-allocation
  - network-configuration
tools:
  allowed:
    - mcp__claude-flow__swarm_init
    - mcp__claude-flow__topology_optimize
    - mcp__claude-flow__memory_usage
    - TodoWrite
  restricted:
    - Bash
    - Write
    - Edit
triggers:
  - pattern: "init.*swarm|create.*swarm|setup.*agents"
    priority: high
  - keyword: "swarm-init"
---

Read the full file on GitHub · 751 lines

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.

  1. 6d ago First seen · 751 lines · 18 tokens per session scan A 8443b2abf465

Subscribe to this mod's changes

agent-migration-plan is a skill published in the GitHub repository ruvnet/ruflo (70,498 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 4,679 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-30.

Related

Other skills, from other repositories

external-memory-plugin

Develop, adapt, review, test, and troubleshoot Nexent external memory provider plugins, including plugin.yaml manifests, searchable and ingestible provider protocols, error mapping, network-isolated unit tests, deployment configuration, and Mem0-based examples. Use when adding a new external memory vendor, changing an…

ModelEngine-Group/nexent · 85 tokens

nw-design

Designs system architecture with C4 diagrams and technology selection. Routes to the right architect based on design scope (system, domain, application, or full stack). Two interaction modes: guide (collaborative Q&A) or propose (architect presents options with trade-offs).

nWave-ai/nWave · 57 tokens

compare-harnesses

Diff two scaffolded harnesses (ADR-031). Reports manifest meta drift + host list + per-file fingerprint changes (added/removed/changed). Exits 0 IDENTICAL, 1 DRIFT, 2 missing manifest. Use --bundle for the ADR-031 schema-1 JSON envelope.

ruvnet/metaharness · 66 tokens

diag-harness

Kernel-version skew check (ADR-027). Reports manifest surface + manifest kernel + installed kernel + verdict (match/patch-diff/minor-diff/major-diff). Exits 1 on minor/major skew with a copy-pasteable npm install @metaharness/[email protected] next step. Exits 2 if no .harness/manifest.json at path.

ruvnet/metaharness · 85 tokens

repo-genome

7-section readiness scorecard for a LOCAL repo. Reports repo type + agent topology + MCP risk + test confidence + release readiness + recommended harness plan + scorecard. Exit 0 ready, 1 needs-work, 2 blocked. --json for the 6-field scorecard, --bundle for the ADR-031 schema-1 envelope.

ruvnet/metaharness · 73 tokens

score-harness

5-dimension scorecard (0-100, grade A/B/C/F) for a scaffolded harness. Dimensions: Repo understanding (25%), Agent usefulness (25%), MCP safety (20%), Test coverage (15%), Publish readiness (15%). Emits a 6-field badges block (score + mcpRisk + 4 booleans) ready for the harness README. Exit 0 A/B, 1 C, 2 F.

ruvnet/metaharness · 0 tokens