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/learnnpx skills add nanocoai/nanoclaw --skill learngit 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/learn)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/learn"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/learn.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.00128 | $0.01471 |
| Opus 5 | $0.00064 | $0.00736 |
| Sonnet 5 | $0.00026 | $0.00294 |
| Haiku 4.5 | $0.00013 | $0.00147 |
Grade A, and why
learn 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Learn — Distill a Skill from Anything
Turn a source — a directory, a URL, pasted notes, or the work just done in this conversation — into a clean, reusable NanoClaw skill. The output is a new .claude/skills/<name>/SKILL.md (plus optional scripts/, references/, templates/) authored to the project's skill guidelines.
This skill is instruction-only: it uses the tools you already have (Read, Grep, Glob, WebFetch, Write) — there is no separate distillation engine and no reach-ins into core code.
When to use
Invoke when the user wants to capture a workflow as a reusable skill:
/learn <path>— read a project/dir and build a skill for working with it/learn <url>— read docs / an API page and build a usage skill/learn what we just did— distill the current conversation's workflow/learn+ pasted notes — turn notes into a structured skill
If the user instead wants to find and install an existing community skill, that is a different task — this skill creates new skills, it does not import them.
Workflow
1. Identify the source — and whether this is a new skill or a refine
- A path → read the code/files.
- A URL → fetch and read the page.
- "what we just did" / "this" → use the current conversation as the source.
- Pasted text → use it directly.
Then check .claude/skills/ for an existing skill that already covers this topic (the user may name it, e.g. "update the wow-on-steam-deck skill", or the subject may obviously match one). If one exists, this is a REFINE, not a fresh create — go to step 4's "Refining" branch.
If it is ambiguous what the skill should do, ask one clarifying question before proceeding.
2. Gather the material
- Path:
Globthe structure,Readthe key files,Grepfor the important entry points. Read enough to understand the repeatable procedure, not every line. - URL:
WebFetchthe page; pull out the concrete commands/steps, not the prose. - Conversation: re-read what was actually done — the commands, the gotchas, the decisions — and keep the parts that generalize.
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 · 98 lines · 128 tokens per session scan A 944c717924af
learn is a skill published in the GitHub repository nanocoai/nanoclaw (30,703 stars, last pushed yesterday), licensed MIT. It adds 128 tokens to every session and 1,471 once invoked, about $0.0006 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
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…
x-integration
Post tweets, like, reply, retweet, and quote on X (Twitter) using browser automation. Use when the user asks you to interact with X/Twitter.
slack-token-extractor
Refresh expired Slack browser tokens (xoxc/xoxd) using persistent browser sessions. Use when Slack MCP tools fail with authentication errors.
python-heredoc
When running multi-line Python code or code with quotes, apostrophes, or f-strings via Bash, always use heredoc syntax instead of python -c to avoid shell quoting issues.
computer-use
Drive a host desktop through Pynchy's policy-mediated provider plugins when browser automation is inappropriate.