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 skills/slackapi/slack-skills-plugin/create-slack-appnpx skills add slackapi/slack-skills-plugin --skill create-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/create-slack-app)<a href="https://agentmods.dev/skills/slackapi/slack-skills-plugin/create-slack-app"><img src="https://agentmods.dev/badge/skills/slackapi/slack-skills-plugin/create-slack-app.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 | $0.00074 | $0.01997 |
| Opus 5 | $0.00037 | $0.00999 |
| Sonnet 5 | $0.00015 | $0.00399 |
| Haiku 4.5 | $0.00007 | $0.00200 |
Grade A, and why
create-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 4d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Slack App
Help the developer create a Slack app or agent using Bolt for $0.
This skill walks through the full setup: prerequisites, authentication, sandbox creation, project scaffolding from a template, and running the app locally.
Step 1: Check Prerequisites
1a. Detect the Slack CLI command
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 here.
Once resolved, use the detected command name for all CLI commands throughout the rest of this skill. We refer to it as SLACK_CMD below — substitute the actual resolved command name everywhere you see SLACK_CMD.
1b. Verify the CLI version
Run SLACK_CMD version and print the version to confirm everything is working before continuing.
1c. Check language runtime
- If
$0isbolt-js: Runnode --versionto verify Node.js is installed (v18+ required). If not installed, suggestbrew install nodeor point to https://nodejs.org. - If
$0isbolt-python: Runpython3 --versionto verify Python is installed (3.6+ required). If not installed, suggestbrew install python3or point to https://python.org.
Step 2: Authenticate with the Slack CLI
Use the slack:slack-cli skill — Step 5: Authentication (slack auth) — to check the developer's auth status and walk them through SLACK_CMD login if they're not already authenticated.
Wait for confirmation that authentication succeeded before proceeding.
Step 3: Set Up a Developer Sandbox
Run SLACK_CMD sandbox list to check if the developer already has a sandbox.
-
If a sandbox exists: Show it and confirm they want to use it.
-
If no sandbox exists: Tell the developer to create one:
! SLACK_CMD sandbox createAlternatively, they can create one at https://api.slack.com/developer-program/sandboxes or join the Developer Program at https://api.slack.com/developer-program/join.
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.
- 4d ago First seen · 187 lines · 74 tokens per session scan A 4ba2eb423948
create-slack-app is a skill published in the GitHub repository slackapi/slack-skills-plugin (117 stars, last pushed today), licensed MIT. It adds 74 tokens to every session and 1,997 once invoked, about $0.0004 per session on Opus 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…