setup-slack-notifications

An interactive setup command for configuring Slack bot notifications. Slack is a team messaging service, and a bot token is the credential that lets the bot act in a workspace.

In plain words
What is it for?
Use it to configure Slack notifications for Claude Code and verify a token beginning with xoxb-.
Why use it?
It guides users through creating a Slack app, obtaining its bot token, and checking whether an existing token works. This removes the need to remember the setup and verification commands.

Command

Install

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.

agentmods
npx agentmods add commands/bvdr/claude-plugins/setup-slack-notifications
Clone the repo
git clone --depth 1 https://github.com/bvdr/claude-plugins
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,383 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found 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 $0.00027 $0.01383
Opus 5 $0.00014 $0.00691
Sonnet 5 $0.00005 $0.00277
Haiku 4.5 $0.00003 $0.00138

Measured 2d ago against content hash 4497bc69a4fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-slack-notifications 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 2d 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.

curl -s -X POST https://slack.com/api/auth.test \
plugins/bvdr/commands/setup-slack-notifications.md · 185 lines

How it starts

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

Setup Slack Notifications

This skill walks you through configuring a Slack bot token so you can send rich notifications from Claude Code.

Pre-flight Check

Before starting the wizard, check if the token is already configured:

  1. Run echo $SLACK_BOT_TOKEN in Bash to check if it's set
  2. If it starts with xoxb-, the token is already configured. Verify it works:
curl -s -X POST https://slack.com/api/auth.test \
  -H "Authorization: Bearer $SLACK_BOT_TOKEN" \
  -H "Content-Type: application/json" | jq .
  1. If "ok": true, tell the user their token is valid and show the workspace/bot name. Done.
  2. If not set or invalid, proceed with the setup wizard below.

Setup Wizard

Use the AskUserQuestion tool with this single question to determine the user's starting point:

{
  "questions": [
    {
      "question": "Where are you in the Slack bot setup process?",
      "header": "Setup stage",
      "options": [
        {"label": "Start from scratch", "description": "I need to create a Slack app and get a bot token"},
        {"label": "I have a token already", "description": "I already have a xoxb-... bot token ready to configure"},
        {"label": "Check my setup", "description": "I think it's configured, just verify it works"}
      ],
      "multiSelect": false
    }
  ]
}

Path: Start from scratch

Walk the user through these steps. Present them as numbered instructions (not automated — the user does these in their browser):

Step 1 — Create a Slack App

Tell the user:

1. Go to https://api.slack.com/apps
2. Click "Create New App" → "From scratch"
3. Name it whatever you like (e.g. "Claude Notifier")
4. Select your workspace
5. Click "Create App"

Step 2 — Add Bot Token Scopes

Tell the user:

6. In the left sidebar, click "OAuth & Permissions"
7. Scroll down to "Scopes" → "Bot Token Scopes"
8. Click "Add an OAuth Scope" and add these two scopes:
   - chat:write        (send messages to channels the bot is in)
   - chat:write.public (send messages to any public channel)

Read the full file on GitHub · 185 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. 2d ago First seen · 185 lines · 27 tokens per session scan A 4497bc69a4fc

Subscribe to this mod's changes

setup-slack-notifications is a command published in the GitHub repository bvdr/claude-plugins (3 stars, last pushed 2mo ago), licensed MIT. It adds 27 tokens to every session and 1,383 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.