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 configuregit 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/configure)<a href="https://agentmods.dev/skills/jeremylongshore/claude-code-slack-channel/configure"><img src="https://agentmods.dev/badge/skills/jeremylongshore/claude-code-slack-channel/configure/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/configure"><img src="https://agentmods.dev/badge/skills/jeremylongshore/claude-code-slack-channel/configure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to high
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 →
- high Privilege Escalation · line 69 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 116 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium Rogue Agent · line 56 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Privilege Escalation · line 69 Commands invoke sudo or root privileges. Verify this elevated access is necessary and justified.Fix: Avoid sudo/root unless strictly required. Prefer least-privilege patterns. If elevation is needed, document the justification and scope.
- medium Agent Snooping · line 128 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 129 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.00055 | $0.01870 |
| Opus 5 | $0.00028 | $0.00935 |
| Sonnet 5 | $0.00011 | $0.00374 |
| Haiku 4.5 | $0.00006 | $0.00187 |
Grade B, and why
configure scanned grade B with 1 finding 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
chmod 700 ~/.claude/channels/slack How it starts
The opening of the file, as written. The whole thing — 179 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/slack-channel:configure
Overview
Configure the Slack channel with its bot and app-level tokens. This is the only
token-writing path: validate prefixes, write .env with owner-only
permissions, never echo secrets, and return control to the install walkthrough.
Prerequisites
- A Slack app already created (via
/slack-channel:installStep 1 or manually at api.slack.com/apps) with:- the Bot User OAuth Token (
xoxb-...) from OAuth & Permissions, and - the App-Level Token (
xapp-..., scopeconnections:write) from Socket Mode settings.
- the Bot User OAuth Token (
- A writable home directory — state lives at
~/.claude/channels/slack/.
Usage
Pass both tokens as arguments, bot token first. Obtain them directly from the Slack app dashboard and avoid shell history or shared transcripts:
/slack-channel:configure <xoxb-bot-token> <xapp-app-token>
Authentication
- The
xoxb-Bot User OAuth Token represents the installed bot and authorizes Web API calls within its granted bot scopes. - The
xapp-app-level token represents the Slack app and requiresconnections:writeto open the Socket Mode WebSocket. - Prefix checks establish token type, not validity.
install doctorverifies liveness against Slack without printing the credential. - Store tokens only in
~/.claude/channels/slack/.env; never commit them or include them in output, logs, screenshots, or issue reports.
Read references/official-auth.md when creating,
rotating, revoking, or diagnosing either token type.
Instructions
-
Parse the two arguments from
$ARGUMENTS:- First token must start with
xoxb-(Bot User OAuth Token) - Second token must start with
xapp-(App-Level Token)
- First token must start with
-
If either token is missing or has the wrong prefix, show this error and stop:
Error: Two tokens required. - Bot token (starts with xoxb-) from OAuth & Permissions - App token (starts with xapp-) from Socket Mode settings Usage: /slack-channel:configure xoxb-... xapp-...
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.
- today Changed · +47 lines 7125443f82e3
- 10d ago First seen · 132 lines · 55 tokens per session scan B 9739a2273942
configure is a skill published in the GitHub repository jeremylongshore/claude-code-slack-channel (39 stars, last pushed yesterday), licensed Apache-2.0. It adds 55 tokens to every session and 1,870 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
llm-engineering-expert
Build reliable applications on large language models: prompt design, structured output, evaluation, guardrails, and cost and latency control. Use when the user mentions LLMs, prompts, prompt engineering, few-shot examples, structured or JSON output, function calling, hallucination, model evaluation, token costs…
token-budget-check
Analyze markdown files for token budget compliance. Checks word count, section lengths, and overall file size against documentation guidelines. Use proactively when creating or reviewing documentation files, knowledge-copilot pages, or when a doc might be over-budget for agent context loading.
document-chunker
Split documents into overlapping token chunks for RAG pipelines and LLM context windows. Zero dependencies.
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.
mode-builder
Create Tandem custom modes through guided questions, then output one valid mode JSON object for preview and apply.