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/slacknpx skills add ericboehs/claude-plugins --skill 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.00048 | $0.01333 |
| Opus 5 | $0.00024 | $0.00666 |
| Sonnet 5 | $0.00010 | $0.00267 |
| Haiku 4.5 | $0.00005 | $0.00133 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack (slk CLI)
Interact with Slack from the command line using slk (Slack Gem).
Prerequisites
slk must be installed and authenticated. If any command fails with "command not found", suggest running /setup-slack.
Usage
/slack— Show unread messages across all workspaces/slack unread— Same as above/slack messages #channel— Read recent channel messages/slack search "query"— Search messages
Arguments after /slack map directly to slk subcommands.
Commands
Unread messages
# Show unread across all workspaces (default action)
slk unread
# Unread for a specific workspace
slk unread -w oddball
# Include muted channels
slk unread --muted
# Clear all unread
slk unread clear
# Clear unread for a specific channel
slk unread clear #channel
Read channel/DM messages
# Channel messages
slk messages #general
slk messages #eert-teammates-internal
# DM messages
slk messages @alexteal
# From a Slack URL (message + thread context)
slk messages https://oddball-io.slack.com/archives/C123/p456
# Limit number of messages
slk messages #general -n 20
# Messages since a duration or date
slk messages #general --since 1d
slk messages #general --since 7d
slk messages #general --since 2026-02-28
# Include thread replies inline
slk messages #general --threads
# Specific workspace
slk messages #general -w oddball
Read threads
Use the messages command with a Slack message URL — it returns the message and its thread:
slk messages https://oddball-io.slack.com/archives/C123ABC/p1234567890
Search messages
Requires user token (xoxc/xoxs), not bot tokens.
# Basic search
slk search "deploy"
# Filter by channel
slk search "deploy" --in #platform-sre-team
# Filter by user
slk search "vtk" --from @alexteal
# Filter by date
slk search "outage" --after 2026-02-01 --before 2026-03-01
slk search "standup" --on 2026-02-28
# Combine filters
slk search "PR review" --in #eert-teammates-internal --from @tomwarren
# More results
slk search "deploy" -n 50
# Specific workspace
slk search "deploy" -w oddball
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 · 221 lines · 48 tokens per session scan A fcfabe797f4a
slack is a skill published in the GitHub repository ericboehs/claude-plugins (2 stars, last pushed 8d ago), licensed MIT. It adds 48 tokens to every session and 1,333 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.
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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.