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/clawsouls/clawsouls-claude-code-plugin/migrate-openclawnpx skills add clawsouls/clawsouls-claude-code-plugin --skill migrate-openclawgit clone --depth 1 https://github.com/clawsouls/clawsouls-claude-code-pluginWrote 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/clawsouls/clawsouls-claude-code-plugin/migrate-openclaw)<a href="https://agentmods.dev/skills/clawsouls/clawsouls-claude-code-plugin/migrate-openclaw"><img src="https://agentmods.dev/badge/skills/clawsouls/clawsouls-claude-code-plugin/migrate-openclaw.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 | $0.00054 | $0.01854 |
| Opus 5 | $0.00027 | $0.00927 |
| Sonnet 5 | $0.00011 | $0.00371 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
migrate-openclaw 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 4d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate OpenClaw to Claude Code
Converts an OpenClaw workspace into a Claude Code project while preserving Soul Spec compatibility. Unlike a destructive migration, this keeps files portable — they work in both OpenClaw and Claude Code.
When to activate
- User says "migrate openclaw", "switch from openclaw", "convert openclaw"
- User provides an OpenClaw workspace path and wants to use Claude Code
- User asks about moving from OpenClaw/SoulClaw to Claude Code
Phase 1: Detect Source
Search for OpenClaw workspace in this order. Stop at first match:
- Current directory — look for
SOUL.md+AGENTS.md,openclaw.json, or.openclaw/ - Default location — check
~/.openclaw/workspace/ - GitHub URL — if user provides a repo URL, clone to temp dir first
- Ask — if nothing found, prompt user for path
Confirmation markers:
SOUL.mdalongsideAGENTS.mdorUSER.mdopenclaw.json.openclaw/directory
Phase 2: Scan & Categorize
Read every file in the source. Categorize into three buckets:
MIGRATE — Becomes part of Claude Code project
| Source File | Destination | Method |
|---|---|---|
SOUL.md |
./SOUL.md |
Copy as-is (project root, NOT renamed) |
IDENTITY.md |
./IDENTITY.md |
Copy as-is |
USER.md |
./USER.md |
Copy as-is |
AGENTS.md |
./AGENTS.md |
Copy, then clean (see Cleaning Rules) |
MEMORY.md |
./MEMORY.md |
Copy as-is |
memory/*.md |
./memory/ |
Copy all files |
STYLE.md |
./STYLE.md |
Copy if exists |
TOOLS.md |
./TOOLS.md |
Copy if exists, strip OpenClaw-specific tool configs |
Custom skills (skills/*/SKILL.md) |
.claude/skills/*/SKILL.md |
Convert (see Skill Conversion) |
ARCHIVE — Moved to _openclaw_archive/ (nothing lost)
openclaw.json(gateway config)credentials/(channel tokens)agents/*/sessions/(old transcripts)devices/(mobile node pairings)logs/(gateway logs).openclaw/(internal state)cron/(scheduled jobs)BOOTSTRAP.md(first-run ritual)HEARTBEAT.md(periodic task config)- Channel config files (
*-allowFrom.json)
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.
- 4d ago First seen · 205 lines · 54 tokens per session scan A 79bd3a8132dd
migrate-openclaw is a skill published in the GitHub repository clawsouls/clawsouls-claude-code-plugin (2 stars, last pushed 24d ago), licensed Apache-2.0. It adds 54 tokens to every session and 1,854 once invoked, about $0.0003 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-31.
Other skills, from other repositories
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步（architecture-sync）。OpenCode / Claude / Codex / Cursor 通用。.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
taiyi-diagram-c4
TaiyiForge 辅助 — 从代码反推 C4 架构文档（Observed/Inferred 分层 · Mermaid 真源）。OpenCode / Claude / Codex / Cursor 通用。.
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.