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
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/nanocoai/nanoclawnpx agentmods add skills/nanocoai/nanoclaw/slack-agent-flowWrote 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-agent-flow)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/slack-agent-flow"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/slack-agent-flow/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-agent-flow"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/slack-agent-flow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
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 →
- medium Agent Snooping · line 111 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 113 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 170 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00043 | $0.04092 |
| Opus 5 | $0.00022 | $0.02046 |
| Sonnet 5 | $0.00009 | $0.00818 |
| Haiku 4.5 | $0.00004 | $0.00409 |
Grade A, and why
slack-agent-flow 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 7d 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 — 313 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack agent flow (create_agent → provisioned Slack bot)
Composes the Slack extension skills into one conversational flow: a user tells
an existing Slack-wired agent "create an agent called Research", and the new
agent doesn't just exist as a send_message destination — it arrives in Slack
as its own bot. The host provisions a Slack app for it (managed broker, or
a workspace manager token), registers it as a slack-<name> instance,
hot-starts the adapter in the running host, opens a DM between the new bot and
the operator, opens a three-way MPIM (operator + originating bot + new bot)
registered as an agent-to-agent room, and wires everything so both agents hear
the room. The flow also adds two agent-facing room actions — create_room
(one shared room with N agents at once, the team primitive) and add_to_room
(grow a room by one agent) — and extends the base create_agent tool with the
flow's purpose / allow_guests / room parameters. Non-Slack sessions are
untouched: create_agent from any other channel behaves exactly as upstream.
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. The
payload the Apply steps fetch with from-branch:channels stays on the
channels branch, exactly like /add-slack's own.
Prerequisites
All prose below assumes these are already in place, in this order:
add-slack— the Slack channel install (src/channels/slack.tsand the shared channel-layer libsrc/channels/slack-lib.tspresent, withslack.tsexporting itsSLACK_DEFAULTSdeclaration and the multi-instance factoryslackInstanceBridgeFactory— the adapter ownsSLACK_INSTANCESregistration natively, and the flow writes each new agent's tokens under that env-key scheme).slack-a2a-rooms— the bot-sender room policy (src/channels/slack-a2a.tspresent), so shared rooms admit the sibling bots' posts.- A provisioning credential in
.env—NANOCLAW_INSTALL_TOKEN(managed broker) orSLACK_MANAGER_TOKEN(direct workspace-level app creation). Without one, agent creation still works but the Slack leg reportsno-credentialsand points at the finish script. - At least one Slack owner/admin in
user_roles— the flow resolves "the operator" from the approver chain (scoped admins → global admins → owners) and needs aslack:U…identity there to open the DM and the room.
What ships with it
25 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.
- apply-fixtures.json 355 B
- container/agent-runner/src/mcp-tools/create-agent-slack.instructions.md 1.7 KB
- container/agent-runner/src/mcp-tools/rooms.instructions.md 1.7 KB
- container/agent-runner/src/mcp-tools/rooms.test.ts 5.0 KB runs code
- container/agent-runner/src/mcp-tools/rooms.ts 7.4 KB runs code
- container/skills/slack-construct-agents/instructions.md 1.8 KB
- container/skills/slack-construct-agents/SKILL.md 1.2 KB
- container/skills/welcome/addenda/teams-tour.md 625 B
- REMOVE.md 2.0 KB
- scripts/slack-agent-flow-finish.ts 5.9 KB runs code
- src/modules/slack-agent-flow/env-file.test.ts 5.1 KB runs code
- src/modules/slack-agent-flow/env-file.ts 3.5 KB runs code
- src/modules/slack-agent-flow/guard.ts 2.7 KB runs code
- src/modules/slack-agent-flow/index.ts 12 KB runs code
- src/modules/slack-agent-flow/orchestrate.test.ts 41 KB runs code
- src/modules/slack-agent-flow/orchestrate.ts 30 KB runs code
- src/modules/slack-agent-flow/provision.congruence.test.ts 14 KB runs code
- src/modules/slack-agent-flow/provision.prefetch.test.ts 2.8 KB runs code
- src/modules/slack-agent-flow/provision.ts 31 KB runs code
- src/modules/slack-agent-flow/room-actions.test.ts 20 KB runs code
- src/modules/slack-agent-flow/room-actions.ts 20 KB runs code
- src/modules/slack-agent-flow/room-canvas.test.ts 9.1 KB runs code
- src/modules/slack-agent-flow/room-canvas.ts 10 KB runs code
- src/modules/slack-agent-flow/slack-deps.ts 3.0 KB runs code
- src/modules/slack-agent-flow/types.ts 4.0 KB runs code
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.
- 7d ago First seen · 313 lines · 43 tokens per session scan A dbcd692b49bf
slack-agent-flow is a skill published in the GitHub repository nanocoai/nanoclaw (30,720 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 4,092 once invoked, about $0.0002 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.