channel-operations

A playbook for setting up, checking, and safely using chat channels with an agent.

In plain words
What is it for?
Use it to catalog channels, save setup details, run diagnostics, test integrations, monitor listeners, prepare messages, and send through an outbox.
Why use it?
It provides an ordered way to inspect channel support, configure connections, diagnose problems, and verify readiness before 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/channel-operations
Any agent
npx skills add CodeInfinity1/Stram --skill channel-operations
Clone the repo
git clone --depth 1 https://github.com/CodeInfinity1/Stram

Made for: Claude Code, Codex.

Per session 21 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,062 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.00021 $0.01062
Opus 5 $0.00010 $0.00531
Sonnet 5 $0.00004 $0.00212
Haiku 4.5 $0.00002 $0.00106

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

Security

Grade A, and why

channel-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/channel-operations/SKILL.md · 104 lines

How it starts

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

Channel Operations

Tool Map

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

Use this skill when the task involves onboarding, diagnosing, or sending through any chat channel.

First Checks

  1. Call channel_catalog to see supported channels.
  2. Call channel_manifest for the exact selected channel.
  3. Call channel_setup_requirements to read required env vars, fields, direct-send support, and policy defaults.
  4. Call channel_doctor before sending or declaring setup complete.
  5. Call channel_integration_smoke for a non-sending readiness report covering setup, prepared outbox, dry-run send wiring, and listener state.
  6. Call channel_listener_status before declaring the agent is listening.

Setup State

Use channel_setup_save for:

  • enabled
  • conversation_defaults
  • allowlist
  • group_allowlist
  • secret_refs such as {"bot_token":"SLACK_BOT_TOKEN"}
  • notes

Do not put raw tokens, app secrets, OAuth refresh tokens, phone auth state, QR session files, or private keys in setup JSON.

Testing A Channel

For a non-destructive smoke:

  1. Run channel_integration_smoke for the selected channel.
  2. Prepare a message with channel_message_prepare when you need to inspect the exact outbound envelope.
  3. Prepare reactions, file shares, thread replies, pins, typing indicators, or read receipts with channel_action_prepare.
  4. Inspect channel_outbox.
  5. For inbound harness smoke, pass an inbound channel message with explicit requires_response:true.
  6. For webhook smoke, use channel_webhook_ingest with a structured provider payload.
  7. For Telegram listener smoke, use channel_listener_tick after enabling the channel and configuring TELEGRAM_BOT_TOKEN.
  8. Confirm a prepared reply exists only for non-ambient request messages.
  9. For external send smoke, use channel_message_send only with approval and a test recipient or room.

Read the full file on GitHub · 104 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 · 104 lines · 21 tokens per session scan A fe50f0b8a409

Subscribe to this mod's changes

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