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.
npx agentmods add commands/bvdr/claude-plugins/setup-slack-notificationsgit clone --depth 1 https://github.com/bvdr/claude-pluginsWhat 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 | $0.00027 | $0.01383 |
| Opus 5 | $0.00014 | $0.00691 |
| Sonnet 5 | $0.00005 | $0.00277 |
| Haiku 4.5 | $0.00003 | $0.00138 |
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 \ 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:
- Run
echo $SLACK_BOT_TOKENin Bash to check if it's set - 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 .
- If
"ok": true, tell the user their token is valid and show the workspace/bot name. Done. - 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)
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.
- 2d ago First seen · 185 lines · 27 tokens per session scan A 4497bc69a4fc
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.
Other commands, from other repositories
dead-code-scan
Scan for dead code, unused imports, duplicates, and zombie code across the project.
esp-teach
One-time project setup -- discover hardware, find datasheets, persist context to CLAUDE.md.
dead-code-clean
Actively find and remove dead code, unused imports, duplicates, and zombie code.
swift-critique
Critique SwiftUI code for patterns, design, clean code, accessibility, and performance.
rust-critique
Deep code critique — read the target Rust code and apply the full review process. Evaluates soundness, ownership, error handling, type design, async correctness, performance, and architecture. Think like a senior Rust engineer giving honest feedback.
rust-harden
Harden Rust code — replace unwrap with proper error handling, add safety comments to unsafe blocks, enable overflow checks, validate inputs at boundaries. The defensive hardening pass.