discord-operations

A workflow for configuring and operating Discord bots across direct messages, servers, channels, threads, forum threads, reactions, and voice-related spaces.

In plain words
What is it for?
Setting up Discord bots, checking channel and listener readiness, receiving events, preparing messages or actions, and sending approved content.
Why use it?
Discord requires bot credentials, permissions, conversation identifiers, and event settings. The workflow checks these requirements and applies rules that prevent the bot from responding to itself.

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/discord-operations
Any agent
npx skills add CodeInfinity1/Stram --skill discord-operations
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

Made for: Claude Code, Codex.

Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,001 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.00028 $0.01001
Opus 5 $0.00014 $0.00500
Sonnet 5 $0.00006 $0.00200
Haiku 4.5 $0.00003 $0.00100

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

Security

Grade A, and why

discord-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/discord-operations/SKILL.md · 100 lines

How it starts

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

Discord 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 Discord setup, guild channels, DMs, threads, forum threads, reactions, voice, or bot-authored events are involved.

Setup

  1. Create a Discord application and bot.
  2. Enable Message Content Intent when guild messages should be read.
  3. Set DISCORD_BOT_TOKEN.
  4. Use channel, thread, forum thread, or DM channel id as conversation_id.
  5. Save non-secret setup refs with channel_setup_save.
  6. Run channel_doctor for discord.

Workflow

  1. Use channel_setup_requirements to inspect Discord token, conversation ID, delivery, and bot-loop policy requirements.
  2. Save enabled state, channel/thread/DM defaults, allowlists, group allowlists, and secret references with channel_setup_save.
  3. Run channel_setup_status, channel_doctor, and channel_listener_status.
  4. Use channel_integration_smoke for prepared envelope and dry-run send readiness.
  5. Use channel_webhook_ingest with a representative Discord message payload to verify inbound normalization and bot-message handling.
  6. Use channel_message_prepare for visible replies and channel_action_prepare for reactions, file-share requests, thread/forum replies, pins, typing indicators, and read receipts.
  7. Use channel_message_send only after approval and only when DISCORD_BOT_TOKEN is configured.

Permissions

Minimum practical permissions:

  • View Channels
  • Send Messages
  • Read Message History
  • Embed Links
  • Attach Files when media is needed
  • Add Reactions when acknowledgement or approval reactions are needed
  • Send Messages in Threads when thread/forum workflows are needed

Guild Channels

Use guild/channel allowlists. Require mentions by default. Ambient rooms are appropriate for private trusted servers where the assistant should quietly track context.

Read the full file on GitHub · 100 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 · 100 lines · 28 tokens per session scan A 40694619131a

Subscribe to this mod's changes

discord-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 28 tokens to every session and 1,001 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-31.