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/rich627/whatsapp-claude-plugin/setupnpx skills add Rich627/whatsapp-claude-plugin --skill setupgit clone --depth 1 https://github.com/Rich627/whatsapp-claude-pluginWrote 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/rich627/whatsapp-claude-plugin/setup)<a href="https://agentmods.dev/skills/rich627/whatsapp-claude-plugin/setup"><img src="https://agentmods.dev/badge/skills/rich627/whatsapp-claude-plugin/setup.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.01358 |
| Opus 5 | $0.00010 | $0.00679 |
| Sonnet 5 | $0.00004 | $0.00272 |
| Haiku 4.5 | $0.00002 | $0.00136 |
Grade A, and why
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 5d 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WhatsApp Channel Setup
You are guiding the user through first-time WhatsApp channel setup. Follow these phases in order. Be conversational, not robotic. Ask one question at a time.
Phase 1: Welcome & Prerequisites
Tell the user:
- This plugin connects Claude Code to WhatsApp as a linked device (like WhatsApp Web)
- They'll need their phone with WhatsApp open nearby
- The setup takes about 2 minutes
Phase 2: Device Linking
Check the connection status by calling the whatsapp_status tool.
If status is connected:
- Skip to Phase 4. Tell the user they're already linked.
If status is pairing and a qr_image_path is present:
- Read the QR image file and display it to the user.
- Tell them: "Open WhatsApp on your phone → Settings → Linked Devices → Link a Device → scan this QR code"
- If a
pairing_codeis also available, mention: "If you can't scan the QR, tap 'Link with phone number instead' and enter: [code]" - Wait for confirmation. Call
whatsapp_statusagain to check if connection succeeded.
If status is disconnected:
- Tell the user the server needs to start first. They should restart Claude Code with the WhatsApp channel enabled:
Explain that this flag is required every launch — it registers the plugin as a channel so incoming messages wake the session in real time. Without it, tools load but messages sit unanswered until something prompts Claude to check.claude --dangerously-load-development-channels plugin:whatsapp-channel@whatsapp-claude-plugin
Phase 3: Phone Number (Optional)
Ask the user:
"Would you like to save your phone number for future re-pairing? This lets the server offer a numeric pairing code as a backup if QR scanning isn't available. You can skip this."
If yes:
- Ask for their phone number with country code (e.g.,
886912345678, no+or spaces) - Save it to
~/.whatsapp-channel/.env:WHATSAPP_PHONE_NUMBER=<their number> - Confirm it's saved.
If no, skip to Phase 4.
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.
- 5d ago First seen · 113 lines · 21 tokens per session scan A 403884caca2a
setup is a skill published in the GitHub repository Rich627/whatsapp-claude-plugin (79 stars, last pushed yesterday), licensed Apache-2.0. It adds 21 tokens to every session and 1,358 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-30.
Other skills, from other repositories
access
Manage WhatsApp channel access control — approve or deny pairings, add or remove users from the allowlist, set DM policy (pairing/allowlist/disabled), and configure group access. Use when the user asks to pair a contact, approve someone, check who's allowed, revoke access, lock down the channel, or change WhatsApp…
configure
Set up and manage the WhatsApp channel connection. Use when the user wants to connect WhatsApp (scan QR code), check connection status, reset the session, enable or disable voice transcription, or set the transcription language. Triggers on /whatsapp:configure, "set up whatsapp", "scan QR", "enable audio", "reset…
keybindings-help
Use when the user wants to customize keyboard shortcuts, rebind keys, add chord bindings, or modify /.claude/keybindings.json. Examples: "rebind ctrl+s", "add a chord shortcut", "change the submit key", "customize keybindings".
options
Present multiple design options as a vertical stack of anchored turns.
tmux
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
summarize
Summarize or extract text/transcripts from URLs, podcasts, and local files (great fallback for “transcribe this YouTube/video”).