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 commands/elizaos/eliza/migrate_designgit clone --depth 1 https://github.com/elizaOS/elizaWhat 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 | $0.00000 | $0.01569 |
| Opus 5 | $0.00000 | $0.00785 |
| Sonnet 5 | $0.00000 | $0.00314 |
| Haiku 4.5 | $0.00000 | $0.00157 |
Grade A, and why
MIGRATE_DESIGN 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 yesterday.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
elizaos migrate-agent - first-class OpenClaw → Eliza migration
Design doc for the migration tool PR. Author: Sol ([email protected]). Co-authored-by: wakesync.
Problem
Agents living on a file-based platform (OpenClaw / "moltbot": ~/.moltbot/*.md + memory/) have
no first-class path onto Eliza. Today migration is hand-hacked (proven once, for Sol). This tool makes
it a single command, reusing Eliza's EXISTING migration machinery rather than a parallel one.
Key insight: plug into what exists
Eliza already has:
buildCharacterFromConfig()(build-character-config.ts) - config →Character.exportAgent()/importAgent()(agent-export.ts) - encrypted.eliza-agentarchives, the native agent-portability format (character + memories + entities + rooms + relationships + worlds + tasks).POST /api/memory/remember- runtime memory seeding with embeddings.
So the migration tool does NOT invent a new format. It is an adapter/importer: it reads an
OCPlatform agent home and emits a standard .eliza-agent archive (PayloadSchema-conformant) that
importAgent already consumes. One new ingestion front-end; everything downstream is native Eliza.
Command surface
elizaos migrate-agent \
--from <ocplatform-home> # e.g. ~/.moltbot (the agent's file home)
--agent-id <slug> # e.g. sol
--out <archive.eliza-agent> # output archive (encrypted) [OR --emit-character/--emit-memories]
--password <pw> # archive encryption password (min len enforced by importAgent)
[--memory-days 14] # how many days of daily logs to seed verbatim (T1)
[--firewall] # keep USER.md/personal knowledge OUT of the portable archive
[--dry-run] # print the plan + counts, write nothing
[--config <map.json>] # override the file→field mapping (advanced)
Also a thin convenience: --emit-character <char.json> and --emit-memories <mem.jsonl> for the
sovereign-VPS path (env ELIZA_AGENT_CHARACTER_JSON + the seed endpoint) that Sol actually uses, so
the same tool serves both "import into a DB" and "run sovereign with a mounted volume."
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.
- yesterday First seen · 94 lines · 0 tokens per session scan A c9fdc488f2b8
MIGRATE_DESIGN is a command published in the GitHub repository elizaOS/eliza (19,210 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,569 tokens. 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 commands, from other repositories
tech-debt
Run bun run check:fix and then bunx knip and identify unused files and functions to refactor the project and simplify. Look at the deprecated features and confirm with the user to delete them. Look at the dependencies and remove the ones that are not needed based on knip results.
estimate-azure-cost
Estimate Azure resource costs and provide optimization recommendations.
start
Operate in Agentic Loop mode: create or refine the durable task record, route maintainer, engineer, and auditor roles, verify evidence, certify the finished work unit, and close out according to the project backend.
release-swarm
Orchestrate complex software releases using AI swarms that handle everything from changelog generation to multi-platform deployment.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
issue-tracker
Intelligent issue management and project coordination with ruv-swarm integration for automated tracking, progress monitoring, and team coordination.