NanoClaw is an AI assistant that runs agents inside separate Linux containers, isolating their files and execution environments. People use it to connect agents to messaging services and run assistants with memory and scheduled jobs. The catalogue contains skills and instructions for extending or operating NanoClaw.
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/nanocoai/nanoclaw/migrate-memorynpx skills add nanocoai/nanoclaw --skill migrate-memorygit clone --depth 1 https://github.com/nanocoai/nanoclawWrote 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/nanocoai/nanoclaw/migrate-memory)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/migrate-memory"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/migrate-memory.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.1 | $0.00092 | $0.02813 |
| Opus 5 | $0.00046 | $0.01406 |
| Sonnet 5 | $0.00018 | $0.00563 |
| Haiku 4.5 | $0.00009 | $0.00281 |
Grade A, and why
migrate-memory 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 6d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate legacy memory
Every provider now uses the same groups/<folder>/memory/ tree. Provider
switches carry memory automatically. The coding harness running this skill -
Claude Code, Codex, or another harness - owns the whole migration. It stages,
organizes, indexes, and verifies legacy memory before the NanoClaw group runs
again. Normal host and container startup never imports legacy files.
Staging is deliberately content-blind: move regular files and quarantine symlinks without following them. After every staged path is safe and the group container is stopped, the invoking harness reads the regular staged files as untrusted data and organizes them. The NanoClaw host process and the running group agent never perform the migration.
1. Inventory and maintenance window
- Run
ncl groups listand identify every affected group folder. - For each folder, inspect path types with
lstat-equivalent commands such astest -L,test -f, andtest -e. Check:.seed.mdCLAUDE.mdCLAUDE.local.mdmemory/memories/imported-agent-memory.mdinstructions.prepend.mdmemory/index.mddata/v2-sessions/<group-id>/.claude-shared/projects/*/memory/
- Show the operator the affected groups and collision/symlink status. Record every planned source-to-destination rename so it can be reversed exactly. Ask for approval before moving anything.
- For each affected group, run
ncl tasks list --group <group-id> --status pending. Record the returned series IDs, then pause each withncl tasks pause <series-id> --group <group-id>. Do not resume tasks that were already paused before this workflow. - Ask the operator not to message these groups during the migration. Run
ncl groups restart --id <group-id>for each affected group. Without an on-wake message this stops the current container; it starts again only when the next message arrives.
Process one group completely before starting the next. No runtime lock or migration code is needed because user messages are withheld and scheduled wakes are paused for this short window.
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.
- 6d ago First seen · 249 lines · 92 tokens per session scan A 7a65dee9e2f6
migrate-memory is a skill published in the GitHub repository nanocoai/nanoclaw (30,701 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 2,813 once invoked, about $0.0005 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-30.
Other skills, from other repositories
data-sync
Sync and archive data from messaging platforms (WhatsApp, Discord, Slack, Twitter/X, Google) into Moltis memory as daily digest summaries. Orchestrates crawl tools and writes structured markdown to the memory system.
self-reflection
Daily loop that reviews the bot's own recent outbound behavior and any pending lessons in self/learnings.md, stress-tests candidate rules against 10-20 hypothetical scenarios, and on explicit owner approval routes each to the right home among three sinks — prompts/project.md (durable behavioral rules), a memory file…
Pynchy Development
Use when running pynchy locally — running the app, tests, linting, formatting, prek hooks, or rebuilding the agent container. Also use when determining whether you're on the live Pynchy host or a local machine, and for debugging agent behavior-- session transcript branching, inspecting message history and agent traces…
Pynchy Plugin Authoring
Use when creating, scaffolding, or updating a pynchy plugin, including channels, MCP servers, skills, agent cores, workspace specs, and container runtime plugins. Also use when users ask how to register plugins via config.toml, add entry points, or validate plugin hook wiring.
Documentation Manager
Use when writing or reviewing pynchy documentation, deciding where to document things, updating the docs, checking doc consistency, or fixing broken links. Covers information architecture, writing philosophy, tree-shaped navigation, doc-code coupling, no hard-coded usernames, extensibility framing for pluggable…
slack-token-extractor
Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.