sms-operations

A workflow for setting up and sending short text messages (SMS) through Twilio, a service that sends texts from software. It checks phone numbers and requires approval before sending.

In plain words
What is it for?
Preparing urgent reminders, onboarding texts, and other short outbound messages. It also helps diagnose phone-number settings and decide whether SMS is better than email or chat.
Why use it?
It helps prevent messages from going to the wrong number or being sent without review. It also checks whether the Twilio setup is ready.

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

Made for: Claude Code, Codex.

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 513 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.00031 $0.00513
Opus 5 $0.00015 $0.00257
Sonnet 5 $0.00006 $0.00103
Haiku 4.5 $0.00003 $0.00051

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

Security

Grade A, and why

sms-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/sms-operations/SKILL.md · 71 lines

How it starts

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

SMS Operations

Purpose

Use SMS as a minimal, high-signal channel for urgent or simple text communication. Stram's native catalog supports Twilio SMS setup, prepared outbox, and approval-gated direct sends.

When To Use

Use for SMS onboarding, short outbound messages, phone-number channel diagnosis, urgent reminders, or deciding whether SMS is appropriate instead of chat/email.

Inputs And Evidence

  • E.164 recipient phone number as conversation_id.
  • TWILIO_ACCOUNT_SID, TWILIO_AUTH_TOKEN, and TWILIO_FROM_NUMBER readiness.
  • Exact message text and reason.
  • Allowlist or pairing state.

Tool Map

  • channel_manifest
  • channel_setup_requirements
  • channel_setup_status
  • channel_doctor
  • channel_message_prepare
  • channel_message_send
  • message-approval-policy

Workflow

  1. Read the sms manifest and setup requirements.
  2. Confirm the phone number is exact, intended, and allowlisted.
  3. Keep SMS text short and avoid secrets, links when unnecessary, and long explanations.
  4. Prepare the message first with channel_message_prepare.
  5. Run channel_doctor if direct delivery is requested.
  6. Use channel_message_send only after approval and configured Twilio credentials.

Native Implementation Boundaries

  • Use the Stram Twilio SMS adapter only.
  • Do not import external reference SMS plugins or third-party scripts as runtime implementation.
  • MMS/media support must be treated according to the native manifest and adapter result.

Safety And Approval

  • SMS has weak identity guarantees; require strict allowlists.
  • Never send auth codes, API keys, private links, or sensitive logs over SMS.
  • Do not create conversational loops over SMS.

Verification

  • Missing Twilio env vars should appear in channel_doctor.
  • Prepared messages have outbox paths.
  • Sent messages require status: sent from channel_message_send.

Failure Modes

  • Sending a long response better suited to email or chat.
  • Assuming a phone number belongs to a person without evidence.
  • Claiming MMS support when only text was sent.

Read the full file on GitHub · 71 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 · 71 lines · 31 tokens per session scan A 1fa3c8a260bc

Subscribe to this mod's changes

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