What is whatsapp-operations?

A set of instructions for connecting and operating WhatsApp through Stram’s Cloud API or a prepared bridge for trusted local QR connections.

Use it to onboard WhatsApp, check channel health, receive gateway events, prepare and send messages or actions, and inspect the message outbox.

It explains how to choose a connection method, configure the required WhatsApp settings, check the setup, and handle incoming and outgoing messages without guessing the workflow.

whatsapp-operations — Skill for Claude Code and Codex by CodeInfinity1

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.

Any agent

npx skills add CodeInfinity1/Stram --skill whatsapp-operations

Clone the repo

git clone --depth 1 https://github.com/CodeInfinity1/Stram

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/codeinfinity1/stram/whatsapp-operations/github.svg)](https://agentmods.dev/skills/codeinfinity1/stram/whatsapp-operations)

Your own site

<a href="https://agentmods.dev/skills/codeinfinity1/stram/whatsapp-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/whatsapp-operations/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/codeinfinity1/stram/whatsapp-operations"><img src="https://agentmods.dev/badge/skills/codeinfinity1/stram/whatsapp-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,006 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.01006
Opus 5.5	$0.00010	$0.00402
Sonnet 5.5	$0.00005	$0.00201
Haiku 4.5	$0.00002	$0.00101

Measured 1mo ago against content hash 6ff996471877, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

whatsapp-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 1mo 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/whatsapp-operations/SKILL.md · 101 lines

How it starts

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

WhatsApp 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 the task involves WhatsApp onboarding, WhatsApp outbound messages, WhatsApp inbound gateway events, or deciding between Cloud API and personal-account bridge modes.

Modes

Stram owns two WhatsApp paths:

Cloud API text sending through WHATSAPP_ACCESS_TOKEN and WHATSAPP_PHONE_NUMBER_ID.
Prepared outbox envelopes for trusted local QR bridges or personal-account experimentation.

No third-party package is assumed by this skill.

Cloud API Setup

Create a Meta WhatsApp Business app and phone number.
Set WHATSAPP_ACCESS_TOKEN.
Set WHATSAPP_PHONE_NUMBER_ID.
Use the recipient E.164 phone number as conversation_id.
Save non-secret setup refs with channel_setup_save.
Run channel_doctor for whatsapp.

Workflow

Use channel_setup_requirements to decide between Cloud API text send and prepared QR-bridge mode.
Save enabled state, recipient defaults, allowlists, group allowlists, and secret references with channel_setup_save.
Run channel_setup_status, channel_doctor, and channel_listener_status.
Use channel_integration_smoke for prepared envelope and dry-run send readiness.
Use channel_webhook_ingest with a WhatsApp Cloud webhook payload to verify inbound normalization.
Use channel_message_prepare for review, groups, media, or bridge-required paths.
Use channel_message_send only for Cloud API text sends after approval and only when credentials are configured.

Personal QR Bridge Contract

Use this only when the user intentionally wants personal-account behavior.

Rules:

Pairing state stays in the trusted bridge runtime, not in Stram setup JSON.
Stram prepares outbox messages until the bridge is installed and trusted.
Do not broadcast raw WhatsApp inbound content to unrelated plugins unless the user opts in.
Use strict allowlists and separate test numbers/chats when possible.

Read the full file on GitHub · 101 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.

1mo ago First seen · 101 lines · 24 tokens per session scan A 6ff996471877

Subscribe to this mod's changes

whatsapp-operations is a skill published in the GitHub repository CodeInfinity1/Stram (11 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 1,006 once invoked, about $0.0001 per session on Opus 5.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.

ai-agent ai-agents ai-tools desktop-automation desktop-automation-software desktop-automation-windows

android-pentest

A guide for authorized security testing of Android apps, covering APK inspection, runtime testing, traffic capture, code review, and function hooking. An APK is the installable package used by an Android app.

Netw0rkNoob/VulnClaw · 32 tokens

lighting-report-extract

Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.

AlpacaLabsLLC/skills-for-architects · 37 tokens

authentication-patterns

OAuth 2.0, JWT, SSO, MFA, NextAuth/Clerk/Supabase Auth implementation patterns.

travisjneuman/.claude · 28 tokens

container-debugging

Diagnose reported container build, startup, network, permission and resource failures. Use when an image or Compose service fails; reproduce against the final image/config and avoid data-destroying cleanup as a workaround.

WrongStack/WrongStack · 45 tokens

alive:system-upgrade

Upgrade ALIVE to the current version. Handles v1/v2/v3.x source states, multi-surface aware (alive-mcp / Hermes / Codex), retroactive version detection, partial-failure resume, dry-run previews, and rollback inspection.

alivecontext/alive · 57 tokens

pr-review

Comprehensive PR review across six dimensions — cost impact, environment drift, ownership gaps, SOC 2 compliance, deprecated API / version hygiene, and rollback feasibility. Each mode inspects the diff and current file state, reports findings with severity, and recommends concrete fixes. Use when preparing a PR for…

nitinjain999/platform-skills · 81 tokens