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/standup)<a href="https://agentmods.dev/commands/slackapi/slack-skills-plugin/standup"><img src="https://agentmods.dev/badge/commands/slackapi/slack-skills-plugin/standup/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/standup"><img src="https://agentmods.dev/badge/commands/slackapi/slack-skills-plugin/standup.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.00011 | $0.00305 |
| Opus 5.5 | $0.00004 | $0.00122 |
| Sonnet 5.5 | $0.00002 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
standup 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 standup — 11 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
-
Use
slack_read_user_profile(with no user_id) to get the current user's profile information, including their user ID and display name. -
Search for the user's recent messages using
slack_search_publicwith the filterfrom:<@USER_ID>andafter:set to yesterday's date. This captures messages from the last working day. -
Review the messages found and categorize them into standup themes:
- What I worked on — Topics, projects, or tasks the user discussed or contributed to
- What I'm working on next — Any mentions of upcoming work, plans, or follow-ups
- Blockers — Any questions asked that went unanswered, issues raised, or explicit mentions of being stuck
-
For messages in threads, use
slack_read_threadto get the full context so you can accurately describe what the user contributed. -
Format the standup as:
**Standup for <display name> — <today's date>** **Done:** - Item 1 - Item 2 **Doing:** - Item 1 **Blockers:** - None / Item 1 -
Present the standup to the user for review. They can edit, adjust, or ask you to post it to a specific 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.
- 1mo ago First seen · 33 lines · 11 tokens per session scan A 4d7dfa8c9716
standup is a command published in the GitHub repository slackapi/slack-skills-plugin (150 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 305 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 standup, differing in 11 lines, and is treated as a copy.
Other commands, from other repositories
pm-init
Initialize local .pm governance; detect Spec Kit; if absent, analyze the repo and draft a PRD for user confirmation; after confirm/skip run a technical light scan.
pm-all
Full technical governance scan; rebuild .pm/dashboard. Default does not wait on draft PRD. Use --compare-baseline only after a confirmed PRD/charter.
pm-done
Close a todo (TODO-xxx), sync completed.md, refresh overview.
pm-export
Export desensitized governance summary markdown for sharing or machine switch.
pm-outline
Generate detailed project outline and draft charter from user intent (empty/new projects).
pm-status
Show governance health, wizard next step, all open blocking/high todos, and pending review count. Primary daily entry.