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-status)<a href="https://agentmods.dev/skills/bowlofarugula/whatsapp/whatsapp-status"><img src="https://agentmods.dev/badge/skills/bowlofarugula/whatsapp/whatsapp-status/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-status"><img src="https://agentmods.dev/badge/skills/bowlofarugula/whatsapp/whatsapp-status.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.00051 | $0.00698 |
| Opus 5 | $0.00026 | $0.00349 |
| Sonnet 5 | $0.00010 | $0.00140 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
whatsapp-status 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 11d 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.
What it actually says
/whatsapp-status — WhatsApp health check
Run all checks, then report in plain language: one line per check with ✅/❌,
then a "what to do" section only if something failed (point at the matching
/whatsapp-setup step).
- wacli engine present: /whatsapp-setup installs it to
~/.claude/whatsapp/engine—"${CLAUDE_PLUGIN_ROOT:-.}/bin/wacli" --version 2>/dev/null || wacli --version 2>/dev/null || echo MISSING.MISSING→ setup step 1 installs it (fallbackbrew install openclaw/tap/waclior setWACLI_PATH). - bun present:
bun --version || "$HOME/.bun/bin/bun" --version. Missing → setup step 2. - Device linked: call the
statustool (orwacli auth status). Not authenticated → run/whatsapp-setup(or theauthenticatetool): it pops up a QR for them to scan with their phone (ormethod:"code"+ their number for a pairing code) — no terminal. - Local store reachable:
wacli doctor --json 2>&1 | head -40— reports store layout, auth identity, FTS/search state, and counts. A quick content check:wacli chats list --limit 1 --json --read-onlyreturns a chat (or an empty list if nothing has synced yet → suggestwacli sync --once). - MCP tools live: check whether the
send_message/list_chats/read_messages/search_messages/react/watchtools from this plugin's WhatsApp server are available in this session (load via ToolSearch if deferred). If present, the fastest single check is to call thestatustool — it confirms wacli installed, the device linked, and the store reachable in one shot. Missing while 1–4 pass → the session predates the plugin; restart it. - Config: read
~/.claude/whatsapp/config.json(fine if absent) and report the two opt-in safeguards in plain language: the approval gate (approval: true→ every send pauses on a yes/no dialog only the user can answer) and the AI-disclosure signature (signature: true→ "- Sent by Claude for " is appended).
If everything passes, suggest: "WhatsApp yourself a hello, then ask me for your recent messages."
Remind the user once, if relevant: this is their real WhatsApp account on a linked device — keep sends human-paced to avoid rate-limits/bans.
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.
- 11d ago First seen · 44 lines · 51 tokens per session scan A 1fac7db00d64
whatsapp-status is a skill published in the GitHub repository bowlofarugula/whatsapp (0 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 51 tokens to every session and 698 once invoked, about $0.0003 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.