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.02059 |
| Opus 5 | $0.00037 | $0.01030 |
| Sonnet 5 | $0.00015 | $0.00412 |
| Haiku 4.5 | $0.00007 | $0.00206 |
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 10d 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 — 166 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 skill is the
terminal-side half of the access-control model: it approves pairing codes,
sets the DM policy, maintains the user allowlist, and opts channels in or out
with an interaction mode. Every subcommand reads and rewrites the single state
file (access.json) atomically.
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:
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 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.
- 10d 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 (39 stars, last pushed yesterday), licensed Apache-2.0. It adds 74 tokens to every session and 2,059 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
c-slack
Send messages and upload files to Slack channels using the slack CLI. Supports direct messages, channel posts, file uploads, and thread replies.
bot-state
Show where this bot's memory actually lives — state root, summaries, attachments, outbox, buffer, sessions — and what is in each. Use when asked where files go, why a summary or attachment is missing, or to check the bot's storage layout.
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.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.