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 skills add pierreraii/claude-slack-bridge --skill configuregit clone --depth 1 https://github.com/pierreraii/claude-slack-bridgeWrote 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/pierreraii/claude-slack-bridge/configure)<a href="https://agentmods.dev/skills/pierreraii/claude-slack-bridge/configure"><img src="https://agentmods.dev/badge/skills/pierreraii/claude-slack-bridge/configure/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/pierreraii/claude-slack-bridge/configure"><img src="https://agentmods.dev/badge/skills/pierreraii/claude-slack-bridge/configure.svg" alt="Reviewed on agentmods" width="80" 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.00056 | $0.00767 |
| Opus 5 | $0.00028 | $0.00383 |
| Sonnet 5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00006 | $0.00077 |
Grade B, and why
configure scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
5. `chmod 600 ~/.claude/channels/slack/.env` How it starts
The opening of the file, as written. The whole thing — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/slack-bridge:configure — Slack Channel Setup
Writes the bot and app tokens to ~/.claude/channels/slack/.env and orients the
user on access policy. The server reads this file at boot.
Arguments passed: $ARGUMENTS
Dispatch on arguments
No args — status and guidance
Read both state files and give the user a complete picture:
-
Tokens — check
~/.claude/channels/slack/.envforSLACK_BOT_TOKENandSLACK_APP_TOKEN. Show set/not-set; if set, show first 10 chars masked. -
Access — read
~/.claude/channels/slack/access.json(missing = defaults). Show: dmPolicy, allowed senders count and list, pending pairings. -
What next — concrete next step:
- No tokens → show the Slack App setup guide below
- Tokens set, nobody allowed → "DM your bot on Slack. Approve with
/slack-bridge:access pair <code>." - Tokens set, someone allowed → "Ready. DM your bot to reach the assistant."
Push toward lockdown. Once the allowlist is set, offer to flip to allowlist policy.
<bot-token> <app-token> — save tokens
- Split
$ARGUMENTS— first isSLACK_BOT_TOKEN, second isSLACK_APP_TOKEN. - Warn if prefixes don't match
xoxb-/xapp-. mkdir -p ~/.claude/channels/slack- Read existing
.env, update/add both lines, preserve other keys. Write back. chmod 600 ~/.claude/channels/slack/.env- Show no-args status after saving.
- Note: restart required for token changes (
/reload-plugins).
clear — remove tokens
Delete both token lines (or the file if that's all it contains).
Slack App Setup Guide
Show this when tokens are not set:
To create a Slack bot:
1. Go to https://api.slack.com/apps → "Create New App" → "From scratch"
2. Left sidebar → "Socket Mode" → Enable Socket Mode
Generate an App-Level Token with scope: connections:write
Copy it — this is your SLACK_APP_TOKEN (starts with xapp-)
3. Left sidebar → "OAuth & Permissions" → "Bot Token Scopes" → Add:
chat:write, reactions:write, im:history, im:write,
channels:history, groups:history, files:read, files:write, users:read
4. Left sidebar → "Event Subscriptions" → Enable Events → Subscribe to:
message.im, message.channels, message.groups, app_mention
5. Left sidebar → "Install App" → "Install to Workspace" → Allow
Copy the Bot User OAuth Token — this is your SLACK_BOT_TOKEN (starts with xoxb-)
6. Run: /slack-bridge:configure xoxb-... xapp-...
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 · 84 lines · 56 tokens per session scan B 81703e4a1c7c
configure is a skill published in the GitHub repository pierreraii/claude-slack-bridge (1 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 56 tokens to every session and 767 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
build-design-workflow
Configure the design phase of the /process workflow. Asks whether the user wants a design step at all (skip-able), then asks whether they already have a design process (e.g. an existing /design command or skill). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets…
build-plan-workflow
Configure the plan phase of the /process workflow. Asks whether the user wants a plan step at all (skip-able), then asks whether they already have a planning process (e.g. an existing /plan command or skill). If they do, reads it and inspects whether it already commits/pushes/opens a PR; whatever is missing gets…
build-process-skill
Generate the /process orchestrator command for this repo. Writes .claude/commands/process.md — the local entry point that reads .claude/process-template.json and walks through the configured workflow steps in order, dispatching to each step's slash command and routing to /required-fixes when a /review step surfaces…
build-run-plan-flow
Configure the run-plan (implementation) phase of the /process workflow. Asks whether the user wants a run-plan step at all (skip-able), then asks whether they already have a run-plan process (e.g. an existing /run-plan command or skill that takes a plan doc and implements it). If they do, reads it and inspects whether…
slack-webhook
Send the user a Slack message as Claude — progress, a finished task, an alert, anything worth interrupting them for. Use whenever you want to reach the user outside this chat. Required instead of the Slack connector, which posts as the user and doesn't notify them.
slack-expert
Expert in Slack bot development, Block Kit UI, Events API, slash commands, OAuth flows, and app distribution. Use when the user mentions communication, collaboration, bots, API, Slack bot, or Block Kit, or when the task involves Slack Platform, Development Tools, Slack Bot with Bolt, or Python Slack Bot.