Borrowing it
Nothing to install: this file belongs to chiptoe-svg/nanoclaw_flexagents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/chiptoe-svg/nanoclaw_flexagents/main/.claude/skills/migrate-from-openclaw/SKILL.mdgit clone --depth 1 https://github.com/chiptoe-svg/nanoclaw_flexagentsWrote 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/chiptoe-svg/nanoclaw_flexagents/migrate-from-openclaw)<a href="https://agentmods.dev/skills/chiptoe-svg/nanoclaw_flexagents/migrate-from-openclaw"><img src="https://agentmods.dev/badge/skills/chiptoe-svg/nanoclaw_flexagents/migrate-from-openclaw/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/chiptoe-svg/nanoclaw_flexagents/migrate-from-openclaw"><img src="https://agentmods.dev/badge/skills/chiptoe-svg/nanoclaw_flexagents/migrate-from-openclaw.svg" alt="Reviewed on agentmods" width="80" 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.00068 | $0.06918 |
| Opus 5 | $0.00034 | $0.03459 |
| Sonnet 5 | $0.00014 | $0.01384 |
| Haiku 4.5 | $0.00007 | $0.00692 |
Grade A, and why
migrate-from-openclaw scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- For simple webhook notifications: a task script with `curl` often suffices This is a copy
98% identical to migrate-from-openclaw — 12 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 — 448 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate from OpenClaw
Guide the user through migrating their OpenClaw installation to NanoClaw. This is a conversation, not a batch job. Read OpenClaw state, discuss it with the user, make judgment calls together about what to bring over and how.
Principle: Never silently copy data. Read it, explain it, discuss where it belongs in NanoClaw's architecture, show proposed changes before applying. Credentials must be masked when displayed (first 4 + ... + last 4 characters). Make judgment calls about what's core vs. reference material.
UX: Use AskUserQuestion for multiple-choice only. Use plain text for free-form input. Don't dump raw data — summarize and explain conversationally.
Migration State File
Create migration-state.md in the project root at the start of Phase 0. Update it after each phase completes. This file is the single source of truth for the migration — if context is compacted or lost, re-read it to recover all decisions and progress.
Before starting any phase, re-read migration-state.md to ensure you have current state.
Sections to maintain (add data as each phase completes):
- Progress — checkbox list of phases (Phase 0–7)
- Discovery — STATE_DIR, IDENTITY_NAME, channels, groups (with JID mappings), workspace files, cron job count, MCP servers
- Decisions — assistant_name, group_model (shared/separate/main-only), main_group (folder + jid)
- Registered Groups — table: folder, jid, channel, is_main
- Settings Migrated — timezone, anthropic_credential (masked), sender_allowlist (created/skipped)
- Identity & Memory — paths of files created, which CLAUDE.md was edited
- Channel Credentials — table: channel, status, env_var
- Scheduled Tasks — table: original_id, name, migrated/deferred
- Deferred / Not Applicable — unsupported channels, discussed customizations, OpenClaw-only features
Keep it factual and terse — this is for machine recovery after compaction, not human reading. Delete the file at the end of Phase 7 (or offer to keep it as a record).
What ships with it
3 files 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.
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.
- 11d ago First seen · 448 lines · 68 tokens per session scan A 92b9fa0d6c43
migrate-from-openclaw is a skill published in the GitHub repository chiptoe-svg/nanoclaw_flexagents (5 stars, last pushed 4mo ago), licensed MIT. It adds 68 tokens to every session and 6,918 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 98% identical to migrate-from-openclaw, differing in 12 lines, and is treated as a copy.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.