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/init-first-agentnpx skills add nanocoai/nanoclaw --skill init-first-agentgit 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/init-first-agent)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/init-first-agent"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/init-first-agent.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.00056 | $0.02367 |
| Opus 5 | $0.00028 | $0.01184 |
| Sonnet 5 | $0.00011 | $0.00473 |
| Haiku 4.5 | $0.00006 | $0.00237 |
Grade A, and why
init-first-agent 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- init-first-agent — 88% identical, 51 lines differ
- init-first-agent — 86% identical, 47 lines differ
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init First Agent
Wire the first NanoClaw agent to a channel and verify end-to-end delivery by having the agent DM the operator. Everything the skill does is idempotent — rerunning is safe.
Prerequisites
- Service running. Check:
launchctl list | grep "$(. setup/lib/install-slug.sh && launchd_label)"(macOS) orsystemctl --user status "$(. setup/lib/install-slug.sh && systemd_unit)"(Linux). If stopped, tell the user to run/setupfirst. - Target channel installed. At least one
/add-<channel>skill has run, credentials are in.env, and the adapter is uncommented insrc/channels/index.ts. - Adapter connected. Tail
logs/nanoclaw.log— look for a recentchannel setup/adapter connectedline for the target channel.
1. Pick the channel
Read src/channels/index.ts to find enabled channels (uncommented imports). Cross-check .env for the relevant credentials.
AskUserQuestion: "Which channel should host the welcome DM?" with one option per enabled channel (Discord, Slack, Telegram, WhatsApp, Webex, Teams, Google Chat, Matrix, iMessage, Resend, …).
Record the choice as CHANNEL (lowercase, e.g. discord).
2. Ask for the operator's identity
Read the channel's own skill for its ## Channel Info > how-to-find-id section (e.g. .claude/skills/add-discord/SKILL.md, .claude/skills/add-telegram/SKILL.md). Show those instructions to the user in plain text.
Then ask in plain text (NOT AskUserQuestion — these are free-form):
- Your user id on this channel — e.g. a Discord user ID, Telegram user ID, Slack user ID. Record as
USER_HANDLE. - Your display name — human name, used to name the agent group (
dm-with-<normalized>) and as the welcome-message addressee. Record asDISPLAY_NAME. - Agent persona name — the assistant's display name. Default:
DISPLAY_NAME. Record asAGENT_NAME.
3. Resolve the DM platform id
This depends on whether the channel supports cold DM via adapter.openDM.
Channels without cold DM (direct-addressable): telegram, whatsapp, imessage, matrix, resend. The user handle doubles as the DM chat id. Set:
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 · 146 lines · 56 tokens per session scan A d238431d1437
init-first-agent is a skill published in the GitHub repository nanocoai/nanoclaw (30,708 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 2,367 once invoked, about $0.0003 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 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.
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.
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…
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.