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.
npx agentmods add skills/codeinfinity1/stram/whatsapp-operationsnpx skills add CodeInfinity1/Stram --skill whatsapp-operationsgit clone --depth 1 https://github.com/CodeInfinity1/StramWhat 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 | $0.00024 | $0.01006 |
| Opus 5 | $0.00012 | $0.00503 |
| Sonnet 5 | $0.00005 | $0.00201 |
| Haiku 4.5 | $0.00002 | $0.00101 |
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 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.
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_manifestchannel_setup_requirementschannel_setup_savechannel_setup_statuschannel_doctorchannel_listener_statuschannel_webhook_ingestchannel_message_preparechannel_action_preparechannel_message_sendchannel_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_TOKENandWHATSAPP_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_doctorforwhatsapp.
Workflow
- Use
channel_setup_requirementsto 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, andchannel_listener_status. - Use
channel_integration_smokefor prepared envelope and dry-run send readiness. - Use
channel_webhook_ingestwith a WhatsApp Cloud webhook payload to verify inbound normalization. - Use
channel_message_preparefor review, groups, media, or bridge-required paths. - Use
channel_message_sendonly 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.
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.
- 2d ago First seen · 101 lines · 24 tokens per session scan A 6ff996471877
whatsapp-operations is a skill published in the GitHub repository CodeInfinity1/Stram (10 stars, last pushed 22d ago), licensed MIT. It adds 24 tokens to every session and 1,006 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.
Other skills, from other repositories
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
golden-rss
Use when testing the rss golden build.
omh-code-review
This is a Hermes-native code-review workflow skill.
redteam-web-detail-pack
Routing and boundary guidance for authorized general web application security testing. Use as a web testing router when the attack surface should be dispatched to more specific web vulnerability skills.
android-pentest
安卓应用渗透测试 — APK分析、Hook、自动化测试、运行态驱动、签名恢复、抓包分析.
studio
Architecture Studio control plane — initialize or inspect a studio workspace, create and register projects, or route an architecture/AEC task to the right agent or skill. Use when the user runs /as:studio, asks to set up or open their studio, manage its projects, or describes a task without naming a skill.