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 skills add riasistemas/claude-channel-whatsapp --skill configuregit clone --depth 1 https://github.com/riasistemas/claude-channel-whatsappWrote 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.
[](https://agentmods.dev/skills/riasistemas/claude-channel-whatsapp/configure)<a href="https://agentmods.dev/skills/riasistemas/claude-channel-whatsapp/configure"><img src="https://agentmods.dev/badge/skills/riasistemas/claude-channel-whatsapp/configure/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.
<a href="https://agentmods.dev/skills/riasistemas/claude-channel-whatsapp/configure"><img src="https://agentmods.dev/badge/skills/riasistemas/claude-channel-whatsapp/configure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00059 | $0.01674 |
| Opus 5 | $0.00030 | $0.00837 |
| Sonnet 5 | $0.00012 | $0.00335 |
| Haiku 4.5 | $0.00006 | $0.00167 |
Grade B, and why
configure scanned grade B with 1 finding 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 12d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
5. `chmod 600 ~/.claude/channels/whatsapp/.env` — these are credentials. How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/whatsapp:configure — WhatsApp Channel Setup
Writes WhatsApp Cloud API credentials to ~/.claude/channels/whatsapp/.env
and orients the user on access policy. The server reads .env once at boot.
Arguments passed: $ARGUMENTS
Required env vars
The server fails fast if any of these are missing:
| Var | What it is | Where to find it |
|---|---|---|
WHATSAPP_ACCESS_TOKEN |
Long-lived System User token with whatsapp_business_messaging scope |
Meta App Dashboard → System Users → Generate Token |
WHATSAPP_PHONE_NUMBER_ID |
The phone number ID (NOT the phone number itself) | Meta App Dashboard → WhatsApp → API Setup |
WHATSAPP_WABA_ID |
WhatsApp Business Account ID | Meta App Dashboard → WhatsApp → API Setup |
WHATSAPP_VERIFY_TOKEN |
Any random string you choose; you'll paste the same value into Meta's webhook config | Pick a strong random string (e.g. openssl rand -hex 32) |
WHATSAPP_APP_SECRET |
The Meta App Secret used for HMAC-SHA256 signature verification | Meta App Dashboard → App Settings → Basic → App Secret |
Optional:
| Var | Default | Purpose |
|---|---|---|
WHATSAPP_PORT |
3789 |
Local HTTP port for the webhook receiver |
WHATSAPP_SELF_PHONE |
(empty) | Your own WABA phone — used to filter outbound echoes |
WHATSAPP_PERMISSION_TARGET |
(empty) | Phone allowed to answer Claude's permission prompts |
WHATSAPP_PHONE_REGION |
intl |
Set to BR to enable Brazilian DDD9 matching heuristics |
WHATSAPP_TIMEZONE |
UTC |
IANA timezone for local_time in notifications |
WHATSAPP_STATE_DIR |
~/.claude/channels/whatsapp |
Override the state directory |
Dispatch on arguments
Parse $ARGUMENTS (whitespace-separated). If empty or unrecognized, show status.
No args — status and guidance
Read state files and give the user a complete picture:
- Credentials — check
~/.claude/channels/whatsapp/.env. For each required key, show set/not-set; if set, mask everything except the first 6 and last 4 chars.
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.
- 12d ago First seen · 144 lines · 59 tokens per session scan B 10fc697dd2d6
configure is a skill published in the GitHub repository riasistemas/claude-channel-whatsapp (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 59 tokens to every session and 1,674 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…