Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bowlofarugula/whatsapp/plugin install 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/bowlofarugula/whatsapp/whatsapp-setup)<a href="https://agentmods.dev/skills/bowlofarugula/whatsapp/whatsapp-setup"><img src="https://agentmods.dev/badge/skills/bowlofarugula/whatsapp/whatsapp-setup/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/bowlofarugula/whatsapp/whatsapp-setup"><img src="https://agentmods.dev/badge/skills/bowlofarugula/whatsapp/whatsapp-setup.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.00098 | $0.02904 |
| Opus 5 | $0.00049 | $0.01452 |
| Sonnet 5 | $0.00020 | $0.00581 |
| Haiku 4.5 | $0.00010 | $0.00290 |
Grade A, and why
whatsapp-setup 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 9d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/whatsapp-setup — WhatsApp connector setup
After this runs, the user can say "WhatsApp Sam we're confirmed for Friday" or "any new WhatsApp messages from Sam?" in any Claude session, with normal permission prompts before anything is sent. There is no background agent and no auto-reply: Claude only reads or sends when asked.
The WhatsApp engine is wacli, a Go CLI
that pairs as a linked WhatsApp Web device; the plugin ships a thin MCP server
over it that exposes authenticate (device linking), send_message,
list_chats, read_messages, search_messages, react, watch, and
status in every session.
The user may be non-technical and is probably in the Claude desktop app, not a terminal. Linking happens right here in chat — no terminal. Run every check yourself; the only thing they do by hand is scan a QR with their phone (or type one short code, if they prefer).
Arguments passed: $ARGUMENTS (optional)
Step 0 — say the honest caveat first
Before installing anything, tell the user plainly, once:
This links Claude to your real WhatsApp account as a Web device. WhatsApp doesn't officially support third-party Web clients, so automating a linked device carries a low-but-real risk that your number gets rate-limited or banned. Keep messages deliberate and human-paced — no bulk or spammy sends — and that risk stays low. OK to continue?
Only proceed once they're OK with it.
Step 1 — install the wacli engine (you do this, via Bash)
The engine is the official binary from the
openclaw/wacli GitHub release. You
download and install it — the user does nothing and needs no Homebrew or
developer tools; macOS's built-in curl/tar do the work. First check
whether it's already there:
"$HOME/.claude/whatsapp/engine/wacli" --version 2>/dev/null || wacli --version 2>/dev/null || echo MISSING
A version number → done, skip to Step 2.
MISSING on macOS → install it (pinned version, checksum-verified; the
universal binary covers Apple Silicon and Intel):
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.
- 9d ago First seen · 240 lines · 98 tokens per session scan F 519cb824e889
whatsapp-setup is a skill published in the GitHub repository bowlofarugula/whatsapp (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 2,904 once invoked, about $0.0005 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
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…