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.
npx agentmods add skills/henryalouf/ruflow/agent-migration-plannpx skills add henryalouf/ruflow --skill agent-migration-plangit clone --depth 1 https://github.com/henryalouf/ruflowWrote 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/henryalouf/ruflow/agent-migration-plan)<a href="https://agentmods.dev/skills/henryalouf/ruflow/agent-migration-plan"><img src="https://agentmods.dev/badge/skills/henryalouf/ruflow/agent-migration-plan.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.00018 | $0.04679 |
| Opus 5 | $0.00009 | $0.02339 |
| Sonnet 5 | $0.00004 | $0.00936 |
| Haiku 4.5 | $0.00002 | $0.00468 |
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.
This is a copy
100% identical to agent-migration-plan — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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"
---
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 · 751 lines · 18 tokens per session scan A 8443b2abf465
agent-migration-plan is a skill published in the GitHub repository henryalouf/ruflow (123 stars, last pushed 3mo ago), 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. It is 100% identical to agent-migration-plan, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…