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.
npx skills add slackapi/slack-skills-plugin --skill deploy-slack-appgit 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/skills/slackapi/slack-skills-plugin/deploy-slack-app)<a href="https://agentmods.dev/skills/slackapi/slack-skills-plugin/deploy-slack-app"><img src="https://agentmods.dev/badge/skills/slackapi/slack-skills-plugin/deploy-slack-app/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/slackapi/slack-skills-plugin/deploy-slack-app"><img src="https://agentmods.dev/badge/skills/slackapi/slack-skills-plugin/deploy-slack-app.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.00098 | $0.03902 |
| Opus 5.5 | $0.00039 | $0.01561 |
| Sonnet 5.5 | $0.00020 | $0.00780 |
| Haiku 4.5 | $0.00010 | $0.00390 |
Grade A, and why
deploy-slack-app 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 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.
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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploy Slack App
Take a Slack app that already works locally and deploy it to a hosting provider as a separate Slack app, with its own app ID, that keeps running without the developer's machine. The local development app is unchanged, and Step 5: Deploy explains how the two coexist. This is the step after the slack:test-slack-app skill confirms the app responds.
The mechanism is the Slack CLI's deploy hook. Adding a deploy key to the project's .slack/hooks.json replaces Slack's own hosted deployment with a script of your choosing, and the CLI runs that script after it has created and installed the deployed app. That ordering is the whole reason this approach is worth using: the app's bot and app-level tokens are already in the script's environment by the time it runs, so nothing here has to prompt for a secret or store one.
Two supported providers, both running the app as a long-lived worker process:
| Provider | Process type | Deploys from | Secrets | Current pricing |
|---|---|---|---|---|
| Railway | Service, no port binding required | The working directory | Passed on stdin | https://railway.com/pricing |
| Heroku | worker dyno |
A git push of committed code | Passed as arguments | https://www.heroku.com/pricing |
Railway is the better default, and the reasons are in Step 2a: Choose a Provider.
Step 1: Check Prerequisites
1a. Detect the Slack CLI
Use the slack:slack-cli skill (Step 1: Detect the Slack CLI) to check whether the public Slack CLI is installed and resolve its command name. The fingerprint check, alias fallback, and install instructions all live there; do not duplicate them. Refer to the resolved command as SLACK_CMD throughout.
This matters more than it looks. Some machines have an unrelated internal tool named slack on the path, and running that instead produces confusing failures well into the deploy.
1b. Confirm the App Uses Socket Mode
Read the app's manifest rather than asking. The project already declares which mode it uses, so a question here is redundant. Check manifest.json for settings.socket_mode_enabled. If .slack/config.json sets the manifest source to remote, there is no local file, so read it with SLACK_CMD manifest info instead.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 201 lines · 98 tokens per session scan A af7d181fe42c
deploy-slack-app is a skill published in the GitHub repository slackapi/slack-skills-plugin (160 stars, last pushed yesterday), licensed MIT. It adds 98 tokens to every session and 3,902 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-20.
Other skills, from other repositories
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
signoz-setting-up-observability
Run the full end-to-end observability setup for a service after its telemetry is already flowing into SigNoz: sequence SLI/SLO capture, data exploration (RED/USE), focused dashboards, saved Explorer views, burn-rate and absent-data alerts, and a tuning loop into one opinionated, SLO-aware workflow. Make sure to use…
twelve-factor
Expert Twelve-Factor App methodology assistance covering declarative setup, environment configuration, backing service bindings, stateless processes, and concurrency models. Use when architecting cloud-native applications, containerizing web services, or standardizing 12-factor compliance.
azure
Expert Microsoft Azure cloud assistance covering Entra ID, App Services, AKS, Azure SQL, Blob Storage, and Resource Manager. Use when designing, deploying, and managing enterprise Azure cloud infrastructure.
cloudflare
Expert Cloudflare assistance covering Workers, Pages, DNS records, CDN caching rules, and DDoS protection. Use when deploying edge applications, configuring DNS, and optimizing web performance.
gcp
Expert Google Cloud Platform (GCP) assistance covering Cloud Run, GKE, Cloud Functions, BigQuery, Pub/Sub, and IAM. Use when architecting and operating scalable, enterprise cloud applications on Google Cloud.