slack-operations

A workflow for setting up and operating Slack as a chat channel, including messages, events, files, reactions, direct messages, and group conversations.

In plain words
What is it for?
Configuring Slack apps, checking setup and listener health, processing inbound events, preparing messages or actions, and sending approved content.
Why use it?
Slack requires app credentials, permissions, event settings, and channel policies. The workflow checks these conditions before receiving or sending messages.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/codeinfinity1/stram/slack-operations
Any agent
npx skills add CodeInfinity1/Stram --skill slack-operations
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

Made for: Claude Code, Codex.

Per session 34 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,291 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00034 $0.01291
Opus 5 $0.00017 $0.00646
Sonnet 5 $0.00007 $0.00258
Haiku 4.5 $0.00003 $0.00129

Measured 2d ago against content hash 613a61822fbc, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

slack-operations 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 2d 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.

skills/communications/slack-operations/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Slack Operations

Tool Map

  • channel_manifest
  • channel_setup_requirements
  • channel_setup_save
  • channel_setup_status
  • channel_doctor
  • channel_listener_status
  • channel_webhook_ingest
  • channel_message_prepare
  • channel_action_prepare
  • channel_message_send
  • channel_outbox

Use this skill when Slack setup, diagnosis, inbound events, outbound messages, files, reactions, channels, DMs, or MPIMs are involved.

Setup

  1. Read channel_manifest for slack.
  2. Create a Slack app with the scopes needed for the workflow.
  3. Set SLACK_BOT_TOKEN for outbound messages.
  4. Set SLACK_APP_TOKEN for Socket Mode inbound, or SLACK_SIGNING_SECRET for HTTP Events API verification.
  5. Save non-secret state with channel_setup_save.
  6. Run channel_doctor for slack.

Workflow

  1. Use channel_setup_requirements to confirm Slack required fields, required secrets, delivery mode, and listener policy.
  2. Save only non-secret setup state, allowlists, group allowlists, and secret references with channel_setup_save.
  3. Run channel_setup_status, channel_doctor, and channel_listener_status before claiming Slack is ready.
  4. Use channel_integration_smoke for a non-sending readiness check.
  5. Use channel_webhook_ingest with a representative Slack Events payload to verify inbound normalization and prepared replies.
  6. Use channel_message_prepare and channel_action_prepare to inspect messages, thread replies, reactions, file-share requests, pins, typing indicators, or read receipts.
  7. Use channel_message_send only after approval and only when SLACK_BOT_TOKEN is configured.

Minimum Scopes

For basic DMs and channels:

  • chat:write
  • im:read
  • im:write
  • im:history
  • channels:read
  • channels:history
  • groups:read
  • groups:history
  • app_mentions:read

For richer behavior:

  • files:read
  • files:write
  • reactions:read
  • reactions:write
  • pins:read
  • pins:write
  • mpim:read
  • mpim:history
  • mpim:write

Read the full file on GitHub · 133 lines

Changes

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.

  1. 2d ago First seen · 133 lines · 34 tokens per session scan A 613a61822fbc

Subscribe to this mod's changes

slack-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 34 tokens to every session and 1,291 once invoked, about $0.0002 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-31.