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 iblai/enterprise-agents --skill slackgit clone --depth 1 https://github.com/iblai/enterprise-agentsWrote 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/iblai/enterprise-agents/slack)<a href="https://agentmods.dev/skills/iblai/enterprise-agents/slack"><img src="https://agentmods.dev/badge/skills/iblai/enterprise-agents/slack.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.1 | $0.00029 | $0.00531 |
| Opus 5 | $0.00015 | $0.00266 |
| Sonnet 5 | $0.00006 | $0.00106 |
| Haiku 4.5 | $0.00003 | $0.00053 |
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 7d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Slack
What it is
Slack is the primary team messaging and workflow platform for many enterprise organizations. Agents in this segment use Slack as the delivery channel for responses, meeting summaries, onboarding welcome messages, training reminders, and cross-functional notifications. It is also a source of conversational context when an agent needs to understand what was discussed in a thread or channel.
When to use this skill
- Posting a meeting recap or action-item summary to a channel or thread
- Sending a direct message to a new hire with onboarding instructions
- Delivering a training deadline reminder or compliance alert to individuals or groups
- Reading recent channel messages to provide context for a follow-up task
- Notifying an IT support requester that their ticket has been resolved
Credentials
This skill authenticates using variables from ~/.openclaw/.env (template: .env.example at the config root). Required variables:
SLACK_BOT_TOKEN- OAuth bot token starting withxoxb-SLACK_SIGNING_SECRET- used to verify incoming request signatures (if handling events)
Key operations
POST /api/chat.postMessage- post a message to a channel or DMPOST /api/chat.postEphemeral- send an ephemeral message visible only to one userGET /api/conversations.history?channel=...- fetch recent messages from a channelGET /api/users.lookupByEmail?email=...- resolve a user ID from email addressPOST /api/conversations.open- open a DM channel with a userPOST /api/reactions.add- add an emoji reaction to a message
Notes
- Bot must be invited to any channel it needs to post to or read from.
conversations.historyrequires thechannels:historyorgroups:historyscope depending on channel type.- Rate limits vary by method tier: Tier 1 = 1 req/min, Tier 3 = 50+ req/min.
chat.postMessageis Tier 3. - Avoid storing message content outside the sandbox; treat conversation data as sensitive.
- Use Block Kit for rich formatting (buttons, sections) rather than legacy attachments.
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.
- 7d ago First seen · 38 lines · 29 tokens per session scan A dd6a12f5d1ef
slack is a skill published in the GitHub repository iblai/enterprise-agents (11 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 531 once invoked, about $0.0001 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
timeboxed-iterating
Run a task iteratively over a user-specified duration by dispatching subagents. The orchestrator stays strictly linear and time-checked, but each iteration fans out MULTIPLE subagents in parallel over independent units (and those subagents may fan out further). Shared state — a compact progress digest and a growing…
tmux-layout
Use this skill when the operator wants a prepared tmux visualization layout for the session's side-channels (STATE.md tail, CI-watch, events.jsonl tail). Renders a 4-pane default layout or debug layout. Read-only side-channel observability — the coordinator chat stays in the operator's original terminal. Trigger…
daily
Use this skill when creating today's daily note in the Meta-Vault (03-daily/YYYY-MM-DD.md) with valid vaultFrontmatterSchema-compliant YAML frontmatter. Idempotent: re-running on the same day opens the existing note instead of overwriting. Use when starting a work day, capturing scratch notes, or bootstrapping the…
agent-teams
Multi-agent team orchestration with native Agent Teams. Trigger when the user wants to launch a team of agents, coordinate parallel work with inter-agent communication, or use swarm mode.
usage-guard
Arm proactive 5-hour usage protection for long Claude Code sessions (batch, subagents, high window % at start). Daemon reads account-level 5-hour window usage (not per-session). User types /usage-guard at session start. Re-arm every sitting. If user mentions usage-guard by name, read this file and run arm.sh.
schedule
Use when scheduling recurring cron jobs or one-shot background notifications.