What is openclaw-migration?

A migration tool for moving an OpenClaw setup into Mente, including compatible memories, personality instructions, command approvals, skills, and selected workspace files.

Use it to preview or run a migration, handle conflicts, migrate without secrets, or migrate from a custom OpenClaw folder.

It reduces the manual work of rebuilding an existing OpenClaw configuration and reports items that could not be moved.

openclaw-migration — Skill by chemany

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/chemany/mente/openclaw-migration

Any agent

npx skills add chemany/Mente --skill openclaw-migration

Clone the repo

git clone --depth 1 https://github.com/chemany/Mente

Made for: Claude Code, Codex.

Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 3,681 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 88% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00056	$0.03681
Opus 5	$0.00028	$0.01840
Sonnet 5	$0.00011	$0.00736
Haiku 4.5	$0.00006	$0.00368

Measured 3d ago against content hash f2c0afb54cce, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

openclaw-migration 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 3d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/openclaw_to_hermes.py), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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

This is a copy

88% identical to openclaw-migration — 33 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.

optional-skills/migration/openclaw-migration/SKILL.md · 298 lines

How it starts

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

OpenClaw -> Hermes Migration

Use this skill when a user wants to move their OpenClaw setup into Mente with minimal manual cleanup.

CLI Command

For a quick, non-interactive migration, use the built-in CLI command:

hermes claw migrate              # Full interactive migration
hermes claw migrate --dry-run    # Preview what would be migrated
hermes claw migrate --preset user-data   # Migrate without secrets
hermes claw migrate --overwrite  # Overwrite existing conflicts
hermes claw migrate --source /custom/path/.openclaw  # Custom source

The CLI command runs the same migration script described below. Use this skill (via the agent) when you want an interactive, guided migration with dry-run previews and per-item conflict resolution.

First-time setup: The hermes setup wizard automatically detects ~/.openclaw and offers migration before configuration begins.

What this skill does

It uses scripts/openclaw_to_hermes.py to:

import SOUL.md into the Hermes home directory as SOUL.md
transform OpenClaw MEMORY.md and USER.md into Hermes memory entries
merge OpenClaw command approval patterns into Hermes command_allowlist
migrate Hermes-compatible messaging settings such as TELEGRAM_ALLOWED_USERS and MESSAGING_CWD
copy OpenClaw skills into the active agent home under skills/openclaw-imports/
optionally copy the OpenClaw workspace instructions file into a chosen Hermes workspace
mirror compatible workspace assets such as workspace/tts/ into the active agent home under tts/
archive non-secret docs that do not have a direct Hermes destination
produce a structured report listing migrated items, conflicts, skipped items, and reasons

Path resolution

The helper script lives in this skill directory at:

scripts/openclaw_to_hermes.py

When this skill is installed from the Skills Hub, the normal location is:

${HERMES_HOME:-${MENTE_HOME:-$HOME/.mente}}/skills/migration/openclaw-migration/scripts/openclaw_to_hermes.py

Read the full file on GitHub · 298 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

scripts/openclaw_to_hermes.py 127 KB runs code

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.

3d ago First seen · 298 lines · 56 tokens per session scan A f2c0afb54cce

Subscribe to this mod's changes

openclaw-migration is a skill published in the GitHub repository chemany/Mente (11 stars, last pushed 3mo ago), licensed MIT. It adds 56 tokens to every session and 3,681 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to openclaw-migration, differing in 33 lines, and is treated as a copy.

Building agents Memory and context

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens