slack-skills-plugin is a plugin that connects coding agents to Slack through a Slack MCP server and provides Slack-focused skills for users and developers. It is used with Claude Code, Cursor, Codex, and other coding agents to work with Slack and build Slack applications. The catalogue entries are the plugin's included skills, commands, MCP server, instructions, and settings.
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.
git clone --depth 1 https://github.com/slackapi/slack-skills-pluginWrote 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/commands/slackapi/slack-skills-plugin/summarize-channel)<a href="https://agentmods.dev/commands/slackapi/slack-skills-plugin/summarize-channel"><img src="https://agentmods.dev/badge/commands/slackapi/slack-skills-plugin/summarize-channel/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/commands/slackapi/slack-skills-plugin/summarize-channel"><img src="https://agentmods.dev/badge/commands/slackapi/slack-skills-plugin/summarize-channel.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.00009 | $0.00233 |
| Opus 5.5 | $0.00004 | $0.00093 |
| Sonnet 5.5 | $0.00002 | $0.00047 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
summarize-channel 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 1mo 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.
This is a copy
100% identical to summarize-channel — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Given the channel name provided in $ARGUMENTS (strip any leading #):
- Use the
slack_search_channelstool to find the channel ID for the provided channel name. Strip any leading#from the argument before searching. - Use the
slack_read_channeltool to read recent messages from the channel (default limit of 100 messages). - For any messages that have threads with replies, use
slack_read_threadto read the thread contents so the summary captures threaded discussions. - Produce a concise summary organized by topic or theme. The summary should include:
- An overview of the main topics discussed
- Key decisions or action items mentioned
- Notable announcements or updates
- Active threads and their conclusions (if any)
- Keep the summary scannable — use short bullet points grouped by topic. Mention who said what when it's relevant (e.g., decisions, action items).
- If the channel has very little recent activity, say so and note the last time a message was posted.
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.
- 1mo ago First seen · 17 lines · 9 tokens per session scan A 1719cc1abd99
summarize-channel is a command published in the GitHub repository slackapi/slack-skills-plugin (160 stars, last pushed yesterday), licensed MIT. It adds 9 tokens to every session and 233 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to summarize-channel, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
start-0-4
A setup-progress command that runs a Python script to show the current progress of a project setup.
start-0-4.en
Auto-run by AI: Run uv run python tools/setupprogress.py show to display the current setup progress.
start-0-4.es
Ejecución automática por IA: Ejecute uv run python tools/setupprogress.py show para mostrar el progreso actual de la configuración.
start-11-3.en
Lesson 11-3: News Fetching → Email/Slack Distribution!
start-11-3.es
Leccion 11-3: Obtencion de noticias y distribucion por correo/Slack!
start-11-3
A lesson on building a workflow that fetches news from an RSS feed and distributes it by email or Slack. An RSS feed is a regularly updated list of items from a website.