Agent Migration PlanCAUTION
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Overview
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
6f6a05ecd222OBSERVED · 2026-09-27What it tells the agent
The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.
---
name: agent-migration-plan
description: Agent skill for migration-plan - invoke with $agent-migration-plan
---
---
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:
```yaml
---
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`
```yaml
---
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"
---
```
#### Agent Spawner
**Command**: `.claude$commands$coordination$spawn.md`
```yaml
---
role: coordinator
name: Agent Spawner
responsibilities:
- Create specialized cognitive patterns for task execution
- Assign capabilities to agents based on requirements
- Manage agent lifecycle and resource allocation
capabilities:
- agent-creation
- capability-assignment
- resource-management
- pattern-recognition
tools:
allowed:
- mcp__claude-flow__agent_spawn
- mcp__claude-flow__daa_agent_create
- mcp__claude-flow__agent_list
- mcp__claude-flow__memory_usage
restricted:
- Bash
- Write
- Edit
triggers:
- pattern: "spawn.*agent|create.*agent|add.*agent"
priority: high
- keyword: "agent-spawn"
---
```
#### Task Orchestrator
**Command**: `.claude$commands$coordination$orchestrate.md`
```yaml
---
role: orchestrator
name: Task Orchestrator
responsibilities:
- Decompose complex tasks into manageable subtasks
- Coordinate parallel and sequential execution strategies
- Monitor task progress and dependencies
- Synthesize results from multiple agents
capabilities:
- task-decomposition
- execution-planning
- dependency-management
- result-aggregation
- progress-tracking
tools:
allowed:
- mcp__claude-flow__task_orchestrate
- mcp__claude-flow__task_status
- mcp__claude-flow__task_results
- mcp__claude-flow__parallel_execute
- TodoWrite
- TodoRead
restricted:
- Bash
- Write
- Edit
triggers:
- pattern: "orchestrate|coordinate.*task|manage.*workflow"
priority: high
- keyword: "orchestrate"
---
```
### 2. GitHub Integration Agents
#### PR Manager Agent
**Command**: `.claude$commands$github$pr-manager.md`
```yaml
---
role: github-specialist
name: Pull Request Manager
responsibilities:
- Manage complete pull request lifecycle
- Coordinate multi-reviewer workflows
- Handle merge strategies and conflict resolution
- Track PR progress with issue integration
capabilities:
- pr-creation
- review-coordination
- merge-management
- conflict-resolution
- status-tracking
tools:
allowed:
- Bash # For gh CLI commands
- mcp__claude-flow__swarm_init
- mcp__claude-flow__agent_spawn
- mcp__claude-flow__task_orchestrate
- mcp__claude-flow__memory_usage
- TodoWrite
- Read
restricted:
- Write # Should use gh CLI for GitHub operations
- Edit
triggers:
- pattern: "pr|pull.?request|merge.*request"
priority: high
- keyword: "pr-manager"
---
```
#### Code Review Swarm Agent
**Command**: `.claude$commands$github$code-review-swarm.md`
```yaml
---
role: reviewer
name: Code Review Coordinator
responsibilities:
- Orchestrate multi-agent code reviews
- Ensure code quality and standards compliance
- Coordinate security and performance reviews
- Generate comprehensive review reports
capabilities:
- code-analysis
- quality-assessment
- security-scanning
- performance-review
- report-generation
tools:
allowed:
- Bash # For gh CLI
- Read
- Grep
- mcp__claude-flow__swarm_init
- mcp__claude-flow__agent_spawn
- mcp__claude-flow__github_code_review
- mcp__claude-flow__memory_usage
restricted:
- Write
- Edit
triggers:
- pattern: "review.*code|code.*review|check.*pr"
priority: high
- keyword: "code-review"
---
```
#### Release Manager Agent
**Command**: `.claude$commands$github$release-manager.md`
```yaml
---
role: release-coordinator
name: Release Manager
responsibilitiesTrust audit
CAUTIONgrade B · trust 89/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | NA |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- none-observed
- Network
- none-observed
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- none-found
Findings (4)
crates
plugin/agents
plugin/commands
plugin/skills
Gates applied: no_behavioural_pass.
6f6a05ecd222full audit observations/trust-audit/skill/ruvnet__agent-migration-plan.json · Report an issue / request a re-scanAudit history
Every audit this skill has had.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-09-27 | 6f6a05ecd222 | CAUTION | B | 89 | first audit |
Questions
What does the Agent Migration Plan skill do?
🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
Is Agent Migration Plan safe to install?
With care. The audit graded it B (89/100) and found 4 things worth knowing before you trust this skill, listed below with the exact line each was found on.
What can Agent Migration Plan access on my machine?
The audit observed no filesystem, network or shell use at all in its source.
How current is this page?
The grade is for one exact copy of the source (6f6a05ecd222), read on 2026-09-27. The repository is watched, and a new audit runs when it changes — this is the first audit.