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 skills add nanocoai/nanoclaw --skill update-nanoclawgit 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/update-nanoclaw)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/update-nanoclaw"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/update-nanoclaw/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/nanocoai/nanoclaw/update-nanoclaw"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/update-nanoclaw.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 70 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
- medium Rogue Agent · line 26 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00067 | $0.02683 |
| Opus 5.5 | $0.00027 | $0.01073 |
| Sonnet 5.5 | $0.00013 | $0.00537 |
| Haiku 4.5 | $0.00007 | $0.00268 |
Grade A, and why
update-nanoclaw 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 1mo 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 — 276 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update NanoClaw
Update a customized install through an isolated, resumable transaction. The live checkout is not touched until the staged result has passed validation.
Use ordinary conversation for decisions and confirmations. Do not depend on Claude Code, Codex, OpenCode, or any provider-specific question/skill tool.
Safety contract
- Require a clean live checkout.
- Stage Git integration, dependency installation, installed-skill refresh, and tests in a separate worktree.
- Resolve registry branches from the remote that actually carries them.
- Stop the detected service and drain this install's active containers before changing source mounted into agent containers.
- Snapshot
.env,data/,groups/,store/, and manual-service state before cutover. Sockets and other ephemeral special files are intentionally omitted. - Gate every breaking migration and external version-pin move.
- Stamp the exact Git commit/tree only after all required work succeeds.
- Restart through the detected launchd, user-systemd, system-systemd, or nohup
mode; require process state,
data/ncl.sock, andbin/ncl groups list. - Refuse cutover while an unmanaged
pnpm dev/Node host is running. Stop that process explicitly, update offline, then start it again manually. - On build or health failure, restore Git and the mutable-state snapshot, rebuild the previous image, restart the previous service, and health-check it.
1. Load the newest controller without changing the live tree
Confirm the live tree is clean:
git status --porcelain
Stop if it prints anything. Setup commits the files it applies as
setup: apply <skill> commits unless NANOCLAW_SETUP_COMMIT=0 was set.
Treat anything left as part of the install: show it, ask the user to commit it
as a local customization, then re-check. Never stash it, since the updater
discovers installed skills from these files.
Use the official remote if one already exists. Otherwise add it as upstream:
if git remote get-url upstream >/dev/null 2>&1; then
upstream_remote=upstream
elif git remote get-url origin 2>/dev/null | grep -Eq '(^|[:/])nanocoai/nanoclaw(.git)?$'; then
upstream_remote=origin
else
git remote add upstream https://github.com/nanocoai/nanoclaw.git
upstream_remote=upstream
fi
git fetch "$upstream_remote" --prune
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.
- 1mo ago Changed · +30 lines 631124ad0620
- 1mo ago Changed · +5 lines 5ff18b87b8e9
- 1mo ago Changed · +2 lines 7e1617eb2d3f
- 2mo ago First seen · 239 lines · 67 tokens per session scan A 6f06024bd8d2
update-nanoclaw is a skill published in the GitHub repository nanocoai/nanoclaw (31,086 stars, last pushed yesterday), licensed MIT. It adds 67 tokens to every session and 2,683 once invoked, about $0.0003 per session on Opus 5.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.
update-nanoclaw compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| update-nanoclawnanocoai/nanoclaw | Skill | 31k | yesterday | MIT | A | 67 | Claude Code |
| Pynchy Worktreescrypdick/pynchy | Skill | 10 | 1mo ago | MIT | A | 48 | Claude Code |
| pm-releasekonglong87/superPM | Skill | 86 | 11d ago | MIT | A | 60 | Claude Code |
| gh-issuesKafClaw/KafClaw | Skill | 21 | yesterday | Apache-2.0 | A | 16 | Claude Code, Codex |
| githubKafClaw/KafClaw | Skill | 21 | yesterday | Apache-2.0 | A | 20 | Claude Code, Codex |
| gh-stackmolefrog/moi | Skill | 191 | yesterday | none | A | 80 | Claude Code, Codex |
| Pynchy Developmentcrypdick/pynchy | Skill | 10 | 1mo ago | MIT | A | 79 | Claude Code |