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 slack-a2a-roomsgit 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/slack-a2a-rooms)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/slack-a2a-rooms"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/slack-a2a-rooms/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/slack-a2a-rooms"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/slack-a2a-rooms.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk warn
- NVIDIA SkillSpector pass
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.00121 | $0.03039 |
| Opus 5 | $0.00060 | $0.01520 |
| Sonnet 5 | $0.00024 | $0.00608 |
| Haiku 4.5 | $0.00012 | $0.00304 |
Grade A, and why
slack-a2a-rooms 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 9d 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack agent-to-agent rooms (SLACK_A2A_ROOMS)
Lets two or more NanoClaw Slack bots talk to each other — and to a human — in
a shared group DM (MPIM). Empirically established against live Slack:
conversations.open with users=[<human>, <other bot user id>…] works from a
bot token holding mpim:write and returns an is_mpim channel, and bots
receive each other's messages over their own Socket Mode connections as plain
message events with channel_type: "mpim", bot_id set, and subtype
null.
Canonical home. This directory on main is the skill's canonical source —
the setup wizard and any direct apply read it from the checkout. The copy on
the channels branch is a compatibility mirror for older checkouts whose
setup fetches companions from there; edits land here, never there.
Where sibling-bot messages die today. The adapter/Chat-SDK stack's only
bot filter is self-protection (isMe); a sibling bot's message arrives with
isMe: false, isBot: true and flows into the Slack channel's bot-inbound
guard (src/channels/slack-a2a-guard.ts, installed with /add-slack), which
drops all bot-authored inbound at the bridge boundary by default — before the
router, before any sender-approval flow. The guard exposes a single admission
seam, setBotInboundPolicy; this skill registers the policy that opens it up
selectively:
- Rooms listed in
SLACK_A2A_ROOMS: bot-authored inbound passes, attributed to the user idslack:bot:<bot_id>, under a consecutive-hop limit. - Everywhere else: bot-authored inbound stays dropped at the bridge, exactly as the guard's default already does.
Loop safety. After N consecutive bot-authored inbound messages in an A2A
room without a human message (N = SLACK_A2A_MAX_HOPS, default 6), further
bot messages are dropped with a log line until a human speaks. The counter is
per bot identity and per room; any human message resets it.
Requires:
- The Slack channel installed (
/add-slack), current enough to ship the bot-inbound guard (src/channels/slack-a2a-guard.tswith thesetBotInboundPolicyseam). The default drop arrives with that payload; this skill only adds the allowlisted-room admission on top. - At least two Slack bot identities on this host (or sibling bots on other
hosts sharing the workspace). Named identities are registered natively by
the adapter from
SLACK_INSTANCES— see theslack-multi-instanceskill for the env-key format.scripts/open-a2a-room.tsreads tokens by that convention (SLACK_BOT_TOKEN_<NAME>;default→SLACK_BOT_TOKEN). - Every participating app's manifest must carry the MPIM scopes and event:
mpim:write(open the room),mpim:history+mpim:read(see it), and themessage.mpimbot event (hear it). Apps provisioned through the managed flow (apps.manifest.create+apps.managedInstall) already include all of these.
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.
- 9d ago First seen · 226 lines · 121 tokens per session scan A 6772409dbf4f
slack-a2a-rooms is a skill published in the GitHub repository nanocoai/nanoclaw (30,736 stars, last pushed today), licensed MIT. It adds 121 tokens to every session and 3,039 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-09-02.
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.