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 instructions/bugzy-ai/slack-mcp-server/claude-mdgit clone --depth 1 https://github.com/bugzy-ai/slack-mcp-serverWrote 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/instructions/bugzy-ai/slack-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/bugzy-ai/slack-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/bugzy-ai/slack-mcp-server/claude-md.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.00879 | $0.00879 |
| Opus 5 | $0.00439 | $0.00439 |
| Sonnet 5 | $0.00176 | $0.00176 |
| Haiku 4.5 | $0.00088 | $0.00088 |
Grade A, and why
slack-mcp-server CLAUDE.md scanned grade A with 0 findings 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 5d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
This is a simplified Model Context Protocol (MCP) server that provides AI assistants with standardized access to essential Slack APIs. It's written in TypeScript and uses only stdio transport for direct integration.
Development Commands
Building and Running
npm run build- Compile TypeScript to JavaScript in/distnpm run dev- Start server in development mode with hot reloadingnpm start- Run the production build
Code Quality
npm run lint- Run both ESLint and Prettier checksnpm run fix- Auto-fix all linting issuesnpm run lint:eslint- Run ESLint onlynpm run lint:prettier- Run Prettier only
Examples
npm run examples- Run stdio transport example
Architecture
Core Structure
The server follows a simplified schema-driven design pattern:
-
Request/Response Schemas (
src/schemas.ts):- All Slack API interactions are validated with Zod schemas
- Request schemas define input parameters
- Response schemas filter API responses to only necessary fields
-
Main Server (
src/index.ts):- Stdio-only transport for CLI integration
- Tool registration and request handling
- Single environment variable validation (bot token only)
Transport Mode
- Stdio only: For CLI integration (Claude Desktop, etc.)
Available Tools
All tools follow the pattern: validate request → call Slack API → parse response → return JSON
Core messaging and channel tools (6 total):
slack_list_channels- List public channels with paginationslack_post_message- Post messages to channelsslack_reply_to_thread- Reply to message threadsslack_add_reaction- Add emoji reactions to messagesslack_get_channel_history- Get message history from channelsslack_get_thread_replies- Get all replies in threads
Environment Requirements
Must set in environment or .env file:
SLACK_BOT_TOKEN: Bot User OAuth Token (only token required)
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.
- 5d ago First seen · 99 lines · 879 tokens per session scan A ca6efa429e18
slack-mcp-server CLAUDE.md is an instructions file published in the GitHub repository bugzy-ai/slack-mcp-server (0 stars, last pushed 8mo ago), licensed Apache-2.0. It adds 879 tokens to every session, about $0.0044 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.