agentmods.dev

configure

configure is a skill for Claude Code from eric108lucas/claude-code-slack-channel. It costs 56 tokens per session (866 once invoked), scanned B, original, MIT.

A setup guide for connecting a Slack bot to the coding agent. It saves the bot and app tokens and shows who is allowed to contact it.

In plain words
What is it for?
Use it to configure Slack tokens, review allowed users and pending pairing requests, and get the next setup instruction.
Why use it?
It removes the need to remember where Slack credentials go or how access is controlled. It also helps check whether the connection is ready.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths.

Part of the slack-channel plugin — 2 skills, 1 MCP server shipped together

not rated 4repo 4mo ago B scan 56 tokens original MIT

Good fit Use it to configure Slack tokens, review allowed users and pending pairing requests, and get the next setup instruction.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/eric108lucas/claude-code-slack-channel/configure
View source ↗ eric108lucas/claude-code-slack-channel
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.

Any agent
npx skills add eric108lucas/claude-code-slack-channel --skill configure
Clone the repo
git clone --depth 1 https://github.com/eric108lucas/claude-code-slack-channel

Made for: Claude Code.

Or install slack-channel, the plugin that ships this one along with the rest of its 2 skills, 1 MCP server.

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 configure

README.md
[![agentmods](https://agentmods.dev/badge/skills/eric108lucas/claude-code-slack-channel/configure.svg)](https://agentmods.dev/skills/eric108lucas/claude-code-slack-channel/configure)
Your own site
<a href="https://agentmods.dev/skills/eric108lucas/claude-code-slack-channel/configure"><img src="https://agentmods.dev/badge/skills/eric108lucas/claude-code-slack-channel/configure.svg" alt="Measured on agentmods" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 866 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00056 $0.00866
Opus 5 $0.00028 $0.00433
Sonnet 5 $0.00011 $0.00173
Haiku 4.5 $0.00006 $0.00087

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

Security

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 8d 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.

4. `mkdir -p ~/.claude/channels/slack && chmod 700 ~/.claude/channels/slack`
slack/skills/configure/SKILL.md · 74 lines

How it starts

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

/slack-channel:configure — Slack Channel Setup

Writes Slack tokens to ~/.claude/channels/slack/.env and orients the user on access policy. The server reads both files at boot.

Slack channel needs two tokens (unlike Telegram's one):

  • SLACK_BOT_TOKEN — xoxb-... from OAuth & Permissions → Install to Workspace
  • SLACK_APP_TOKEN — xapp-... from Basic Information → App-Level Tokens (scope: connections:write, needed for Socket Mode)

Arguments: $ARGUMENTS

Dispatch on arguments

No args — status and guidance

  1. Tokens — read ~/.claude/channels/slack/.env. For each of SLACK_BOT_TOKEN and SLACK_APP_TOKEN:
    • Show set/not-set
    • If set, show first 12 chars only (mask the rest)
  2. Access — call list_users MCP tool on slack server. Show:
    • Policy and what it means in one line
    • Allowed users count + IDs
    • Pending pairings count + codes
  3. What next — concrete next step:
    • No tokens → "Run /slack-channel:configure <bot_token> <app_token> with the two tokens from your Slack app dashboard."
    • Tokens set, policy is pairing, nobody allowed → "DM your bot in Slack. It replies with a 6-char code; approve with /slack-channel:access pair <code>."
    • Tokens set, allowlist populated → "Ready. DM the bot to talk to me."

Push toward lockdown. The goal for every setup is allowlist with a defined list. pairing is not a policy to stay on. Once the user has paired themselves and any teammates, offer to switch with /slack-channel:access policy allowlist. Don't wait to be asked.

<bot_token> <app_token> — save them

  1. Treat the first whitespace-separated arg as the bot token. Slack bot tokens look like xoxb-NNNNN-NNNNN-... — xoxb- prefix.
  2. Treat the second arg as the app token. Slack app tokens look like xapp-N-AXXXXXXXX-NNNNN-... — xapp- prefix.
  3. If either prefix doesn't match, refuse and ask the user to double-check.
  4. mkdir -p ~/.claude/channels/slack && chmod 700 ~/.claude/channels/slack
  5. Read existing .env if present; update/add the SLACK_BOT_TOKEN= and SLACK_APP_TOKEN= lines, preserve other keys. Write back, no quotes around values.
  6. chmod 600 ~/.claude/channels/slack/.env — these are credentials.
  7. Confirm and remind the user to restart their session with claude --channels plugin:slack-channel@claude-code-slack-channel (or --dangerously-load-development-channels while the plugin is not on Anthropic's curated allowlist) for the new tokens to take effect.

Read the full file on GitHub · 74 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. 8d ago First seen · 74 lines · 56 tokens per session scan B 86a99f851208

Subscribe to this mod's changes

configure is a skill published in the GitHub repository eric108lucas/claude-code-slack-channel (4 stars, last pushed 4mo ago), licensed MIT. It adds 56 tokens to every session and 866 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.

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

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

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens