nano---Openclaw: Skill for Claude Code

.claude/skills/add-slack/SKILL.md

add-slack is a skill for Claude Code from ShinyStar307/nano---Openclaw. It costs 29 tokens per session (1,976 once invoked), scanned A, a copy of add-slack, MIT.

A setup process that adds Slack, a team messaging service, as a communication channel to NanoClaw.

In plain words
What is it for?
It helps add the Slack channel code, install its dependency, configure access tokens, and run the included tests.
Why use it?
It removes the need to build the Slack connection and its configuration manually.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is ShinyStar307/nano---Openclaw's own configuration. It tells Claude Code how to work on nano---Openclaw itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything nano---Openclaw configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ShinyStar307/nano---Openclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ShinyStar307/nano---Openclaw/main/.claude/skills/add-slack/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ShinyStar307/nano---Openclaw

Made for: Claude Code.

Wrote 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.

agentmods badge for add-slack

README.md
[![agentmods](https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/add-slack/github.svg)](https://agentmods.dev/skills/shinystar307/nano---openclaw/add-slack)
Your own site
<a href="https://agentmods.dev/skills/shinystar307/nano---openclaw/add-slack"><img src="https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/add-slack/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.

agentmods 80×15 button for add-slack

Your own site · 80×15
<a href="https://agentmods.dev/skills/shinystar307/nano---openclaw/add-slack"><img src="https://agentmods.dev/badge/skills/shinystar307/nano---openclaw/add-slack.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,976 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin 86% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01976
Opus 5 $0.00015 $0.00988
Sonnet 5 $0.00006 $0.00395
Haiku 4.5 $0.00003 $0.00198

Measured 9d ago against content hash cf9401961f89, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

add-slack scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- Via API: `curl -s -H "Authorization: Bearer $SLACK_BOT_TOKEN" "https://slack.com/api/conversations.list" | jq '.channels[] | {id, name}'`
Origin

This is a copy

86% identical to add-slack — 78 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/add-slack/SKILL.md · 208 lines

How it starts

The opening of the file, as written. The whole thing — 208 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add Slack Channel

This skill adds Slack support to NanoClaw, then walks through interactive setup.

Phase 1: Pre-flight

Check if already applied

Check if src/channels/slack.ts exists. If it does, skip to Phase 3 (Setup). The code changes are already in place.

Ask the user

Do they already have a Slack app configured? If yes, collect the Bot Token and App Token now. If no, we'll create one in Phase 3.

Phase 2: Apply Code Changes

Ensure channel remote

git remote -v

If slack is missing, add it:

git remote add slack https://github.com/qwibitai/nanoclaw-slack.git

Merge the skill branch

git fetch slack main
git merge slack/main || {
  git checkout --theirs package-lock.json
  git add package-lock.json
  git merge --continue
}

This merges in:

  • src/channels/slack.ts (SlackChannel class with self-registration via registerChannel)
  • src/channels/slack.test.ts (46 unit tests)
  • import './slack.js' appended to the channel barrel file src/channels/index.ts
  • @slack/bolt npm dependency in package.json
  • SLACK_BOT_TOKEN and SLACK_APP_TOKEN in .env.example

If the merge reports conflicts, resolve them by reading the conflicted files and understanding the intent of both sides.

Validate code changes

npm install
npm run build
npx vitest run src/channels/slack.test.ts

All tests must pass (including the new Slack tests) and build must be clean before proceeding.

Phase 3: Setup

Create Slack App (if needed)

If the user doesn't have a Slack app, share SLACK_SETUP.md which has step-by-step instructions with screenshots guidance, troubleshooting, and a token reference table.

Quick summary of what's needed:

  1. Create a Slack app at api.slack.com/apps
  2. Enable Socket Mode and generate an App-Level Token (xapp-...)
  3. Subscribe to bot events: message.channels, message.groups, message.im
  4. Add OAuth scopes: chat:write, channels:history, groups:history, im:history, channels:read, groups:read, users:read
  5. Install to workspace and copy the Bot Token (xoxb-...)

Read the full file on GitHub · 208 lines

Changes

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.

  1. 9d ago First seen · 208 lines · 29 tokens per session scan A cf9401961f89

Subscribe to this mod's changes

add-slack is a skill published in the GitHub repository ShinyStar307/nano---Openclaw (5 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 1,976 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 86% identical to add-slack, differing in 78 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens