Borrowing it
Nothing to install: this file belongs to refactornator/nanoflash. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/refactornator/nanoflash/main/.claude/skills/add-slack/SKILL.mdgit clone --depth 1 https://github.com/refactornator/nanoflashWrote 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/refactornator/nanoflash/add-slack)<a href="https://agentmods.dev/skills/refactornator/nanoflash/add-slack"><img src="https://agentmods.dev/badge/skills/refactornator/nanoflash/add-slack.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.00029 | $0.01976 |
| Opus 5 | $0.00015 | $0.00988 |
| Sonnet 5 | $0.00006 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
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 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.
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}'` 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.
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 viaregisterChannel)src/channels/slack.test.ts(46 unit tests)import './slack.js'appended to the channel barrel filesrc/channels/index.ts@slack/boltnpm dependency inpackage.jsonSLACK_BOT_TOKENandSLACK_APP_TOKENin.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:
- Create a Slack app at api.slack.com/apps
- Enable Socket Mode and generate an App-Level Token (
xapp-...) - Subscribe to bot events:
message.channels,message.groups,message.im - Add OAuth scopes:
chat:write,channels:history,groups:history,im:history,channels:read,groups:read,users:read - Install to workspace and copy the Bot Token (
xoxb-...)
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 · 208 lines · 29 tokens per session scan A cf9401961f89
add-slack is a skill published in the GitHub repository refactornator/nanoflash (5 stars, last pushed 4mo 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…