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/migrate-slack-agentsWrote 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/migrate-slack-agents)<a href="https://agentmods.dev/skills/nanocoai/nanoclaw/migrate-slack-agents"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/migrate-slack-agents/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/migrate-slack-agents"><img src="https://agentmods.dev/badge/skills/nanocoai/nanoclaw/migrate-slack-agents.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Snyk pass
- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 147 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.00075 | $0.03528 |
| Opus 5 | $0.00037 | $0.01764 |
| Sonnet 5 | $0.00015 | $0.00706 |
| Haiku 4.5 | $0.00007 | $0.00353 |
Grade A, and why
migrate-slack-agents 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 10d 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 — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate classic Slack agents
Turn every agent group wired through the classic instance='slack' adapter into
a named slack-<slug> bot without replacing the agent group. This is an
operator-guided, resumable data migration. It never creates an agent group and
never edits an agent workspace.
Migration is optional. Classic single-bot Slack remains fully supported; this skill first offers the choice, and staying on classic is a valid outcome that also satisfies the update requirement.
Hard invariants:
- Never call
create_agentorncl groups create. - Never change an
agent_groups.idor write undergroups/<folder>/. - Never merge the
channelsbranch; fetch and copy skill-owned files only. - Never print token values. Show key names and masked presence only.
- Keep classic rows, credentials, and the shared Slack app available for rollback until the operator explicitly approves cutover.
Phase 1: Detect classic state
Run from the NanoClaw project root. Read the central DB only through the sanctioned wrapper.
Classic state requires all four signals:
-
src/channels/index.tscontains the Slack barrel importimport './slack.js';. -
.envhas a non-empty unsuffixedSLACK_BOT_TOKENand either a non-emptySLACK_APP_TOKENorSLACK_SIGNING_SECRET. Check presence without echoing values. -
This query returns at least one row:
pnpm exec tsx scripts/q.ts data/v2.db "SELECT mg.id, mga.id, mga.agent_group_id FROM messaging_groups mg JOIN messaging_group_agents mga ON mga.messaging_group_id=mg.id WHERE mg.channel_type='slack' AND mg.instance='slack' ORDER BY mg.id, mga.agent_group_id" -
At least one wired group does not yet have complete named-instance coverage: a stable slug, both
SLACK_BOT_TOKEN_<SUFFIX>andSLACK_APP_TOKEN_<SUFFIX>, that slug inSLACK_INSTANCES, and the expectedslack-<slug>messaging-group/wiring rows.
If the classic conjunction is absent and there is no partial state, stop with:
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.
- 10d ago First seen · 294 lines · 75 tokens per session scan A 3f46349e7241
migrate-slack-agents is a skill published in the GitHub repository nanocoai/nanoclaw (30,727 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 3,528 once invoked, about $0.0004 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.