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 jeremylongshore/claude-code-slack-channel --skill accessgit clone --depth 1 https://github.com/jeremylongshore/claude-code-slack-channelWrote 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/jeremylongshore/claude-code-slack-channel/access)<a href="https://agentmods.dev/skills/jeremylongshore/claude-code-slack-channel/access"><img src="https://agentmods.dev/badge/skills/jeremylongshore/claude-code-slack-channel/access/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/jeremylongshore/claude-code-slack-channel/access"><img src="https://agentmods.dev/badge/skills/jeremylongshore/claude-code-slack-channel/access.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 163 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
- medium Agent Snooping · line 164 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00074 | $0.02136 |
| Opus 5.5 | $0.00030 | $0.00854 |
| Sonnet 5.5 | $0.00015 | $0.00427 |
| Haiku 4.5 | $0.00007 | $0.00214 |
Grade A, and why
access 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.
How it starts
The opening of the file, as written. The whole thing — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/slack-channel:access
Overview
Manage who can reach your Claude Code session through Slack. This terminal-only
workflow approves pairing codes, sets the DM policy, maintains allowlists, and
atomically updates channel interaction modes in access.json.
Usage
/slack-channel:access pair <code> # Approve a pending pairing
/slack-channel:access policy <pairing|allowlist|disabled> # Set DM policy
/slack-channel:access add <slack_user_id> # Add user to allowlist
/slack-channel:access remove <slack_user_id> # Remove from allowlist
/slack-channel:access channel <channel_id> [--ambient] [--allow <user_id,...>] # Opt in a channel (default: mention-to-engage)
/slack-channel:access channel remove <channel_id> # Remove channel opt-in
/slack-channel:access status # Show current config
Prerequisites
- A completed install (
/slack-channel:install) — the state directory~/.claude/channels/slack/must exist. - State file:
~/.claude/channels/slack/access.json— every subcommand operates on this one file. It holds the DM policy, allowlist, channel opt-ins, and pending pairing codes, and must stay mode0o600. - For
pair, the MCP server should be running so the confirmation message can be delivered back to the Slack user.
Instructions
Parse $ARGUMENTS and execute the matching subcommand. Use Read to inspect
the complete state and Write only for the complete temporary replacement;
then use mv for the atomic swap and chmod to restore mode 0600.
pair <code>
- Load
access.json - Find the pending entry matching
<code>(case-insensitive) - If not found or expired: show "No pending pairing with that code."
- If found:
- Add
entry.senderIdtoallowFrom - Remove the pending entry
- Save
access.jsonwith permissions 0o600 - Show:
Approved! User <senderId> can now DM this session. - Send a confirmation message to the user in Slack (via the reply tool if the MCP server is running)
- Add
What ships with it
1 file 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.
- 1mo ago Changed · +12 lines dfe34f56f6cc
- 2mo ago First seen · 166 lines · 74 tokens per session scan A 46ba2f1877f2
access is a skill published in the GitHub repository jeremylongshore/claude-code-slack-channel (42 stars, last pushed 3d ago), licensed Apache-2.0. It adds 74 tokens to every session and 2,136 once invoked, about $0.0003 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-08-30.
Other skills, from other repositories
slack-channels
A tool for managing Slack channels, which are shared conversation spaces for teams. It looks up user IDs before inviting people or changing channel settings.
c-slack
Send messages and upload files to Slack channels using the slack CLI. Supports direct messages, channel posts, file uploads, and thread replies.
forge-cli
A command-line management tool for Forge Hub, a service that connects agent instances to chat channels and routes messages between them.
subagent-driven-development
Execute plans via delegatetask subagents (2-stage review).
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.