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/tomeraitz/claude-slack-bridge/process-setupnpx skills add tomeraitz/claude-slack-bridge --skill process-setupgit clone --depth 1 https://github.com/tomeraitz/claude-slack-bridgeWrote 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/tomeraitz/claude-slack-bridge/process-setup)<a href="https://agentmods.dev/skills/tomeraitz/claude-slack-bridge/process-setup"><img src="https://agentmods.dev/badge/skills/tomeraitz/claude-slack-bridge/process-setup.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00155 | $0.02176 |
| Opus 5 | $0.00077 | $0.01088 |
| Sonnet 5 | $0.00031 | $0.00435 |
| Haiku 4.5 | $0.00015 | $0.00218 |
Grade B, and why
process-setup 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 4d 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.
Enumerates other installed skillsmediumAgent snooping
Other skills' SKILL.md files reveal prompts, capabilities and secrets that should be invisible to peers.
prompt: "Read plugin/skills/build-task-manager/SKILL.md (resolve the plugin root via ${CLAUDE_PLUGIN_ROOT} if set, otherwise search upward from cwd until you find plugin.json) and follow it exactly, top to bottom. Use As How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/process-setup — one-time per-repo configuration
You are running the /process-setup skill for the claude-slack-bridge full-process plugin. This is a one-time-per-repo configuration flow. It does NOT start a feature — it only writes the template, optional helper skill, and .gitignore entries that /process will need later.
You run locally inside Claude Code (not via the Slack daemon). All clarifications go through AskUserQuestion. Do not call mcp__claude-slack-bridge__ask_on_slack from this skill — Slack is only the runtime channel for /process itself, not for setup.
The plugin and the daemon's workflow engine are version-locked. The template you write below has version: 1; the daemon checks this on every step spawn and refuses to advance if the version is unsupported. Do not invent a different version.
Step 1 — verify mcp__claude-slack-bridge is installed in the repo (delegated)
Delegate this check to the verify-bridge skill in a separate context. Spawn it via the Agent tool with run_in_background: true so the verification chatter does not pollute this orchestrator's context window:
Agent({
description: "Verify Slack bridge MCP installed",
subagent_type: "general-purpose",
prompt: "Read plugin/skills/verify-bridge/SKILL.md (resolve the plugin root via ${CLAUDE_PLUGIN_ROOT} if set, otherwise search upward from cwd until you find plugin.json). Follow its instructions exactly: read cwd/.mcp.json and confirm a `claude-slack-bridge` entry exists under `mcpServers`. On success, return the literal string 'verify-bridge: ok'. On failure, return the exact fix-it message from the skill and report non-zero status. Do not write any files, do not modify .mcp.json, do not check container runtime health — only verify the declaration.",
run_in_background: true
})
When the subagent's completion notification arrives, branch on the result:
- ok — continue to Step 2.
- failure — print the subagent's returned fix-it message verbatim to the user and exit non-zero. Do not write any files, do not proceed.
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.
- 4d ago First seen · 143 lines · 155 tokens per session scan B 0258825e8ac6
process-setup is a skill published in the GitHub repository tomeraitz/claude-slack-bridge (33 stars, last pushed 14d ago), licensed MIT. It adds 155 tokens to every session and 2,176 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it B with 1 finding (enumerates other installed skills). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
access
Manage Slack channel access — approve pairings, edit allowlists, set DM/channel policy. Use when the user asks to pair, approve someone, check who's allowed, or change policy for the Slack channel.
configure
Set up the Slack channel — save the bot and app tokens and review access policy. Use when the user pastes Slack tokens, asks to configure Slack, asks "how do I set this up" or "who can reach me," or wants to check channel status.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
specflow-use
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
ue-mcp-epic-routing
Use when deciding between ue-mcp's native category actions and Epic's wrapped ToolsetRegistry tools (the epic actions, incl. the Blueprint graph DSL) for a task in Unreal. Pulls in when authoring Blueprint graph bodies, or any time both a native action and an epic action could do the job and you need to pick.
slackdump-source
Explains the different Slackdump sources structure.