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/ericboehs/claude-plugins/setup-slacknpx skills add ericboehs/claude-plugins --skill setup-slackgit clone --depth 1 https://github.com/ericboehs/claude-pluginsWhat 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.00039 | $0.00567 |
| Opus 5 | $0.00019 | $0.00283 |
| Sonnet 5 | $0.00008 | $0.00113 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
setup-slack 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 yesterday.
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.
What it actually says
Setup Slack CLI (slk)
Guided installation and configuration of slk (Slack Gem) for Slack access from the command line.
Step 1: Check Prerequisites
which slk && slk --version
If installed, check for configured workspaces:
slk workspaces
If slk is installed and workspaces are configured, tell the user their Slack CLI is already set up and suggest /slack.
Step 2: Install slk
slk is a Ruby gem. Install via mise (preferred) or gem:
# Via mise (preferred — manages Ruby version automatically)
mise use ruby@latest
gem install slk
# Or directly if Ruby is available
gem install slk
Verify installation:
slk --version
Step 3: Initial Configuration
Run the interactive setup:
slk config setup
This will prompt for:
- Workspace name (e.g., "oddball", "dsva")
- Slack tokens (user token for full access, or bot token for limited access)
User tokens (xoxc/xoxs) provide full access including search. Bot tokens have limited capabilities.
Step 4: Add Workspaces
Add additional workspaces as needed:
slk workspaces add
Common workspaces:
oddball— Oddball team Slackdsva— VA Digital Service Slackboehs— Personal workspace
Step 5: Build Cache
Build the user/channel cache for faster lookups:
slk cache build
slk cache build --all # For all workspaces
Step 6: Set Up Presets (Optional)
Create status presets for quick switching:
slk preset add
Common presets: meeting, focus, lunch, ooo
Step 7: Verify
# Check workspaces
slk workspaces
# Check unread
slk unread
# Test reading a channel
slk messages #general -n 5
Behavior
- Run through steps sequentially, checking what's already done
- Don't reinstall if already present
- If slk is installed but no workspaces configured, skip to Step 3
- After setup, suggest running
/slackto check unread messages
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.
- yesterday First seen · 109 lines · 39 tokens per session scan A 71986614e4f4
setup-slack is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 39 tokens to every session and 567 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…