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 commands/rodrigopg/whatsapp-mcp/setupgit clone --depth 1 https://github.com/rodrigopg/whatsapp-mcpWrote 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/commands/rodrigopg/whatsapp-mcp/setup)<a href="https://agentmods.dev/commands/rodrigopg/whatsapp-mcp/setup"><img src="https://agentmods.dev/badge/commands/rodrigopg/whatsapp-mcp/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.00022 | $0.02864 |
| Opus 5 | $0.00011 | $0.01432 |
| Sonnet 5 | $0.00004 | $0.00573 |
| Haiku 4.5 | $0.00002 | $0.00286 |
Grade B, and why
setup scanned grade B with 2 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 4d 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.
Write the resulting `export VAR=value` lines to `<INSTALL_DIR>/transcription.env` — this file holds a live API key in plaintext, so create it with owner-only permissions from the start (e.g. `(umask 077; cat > "<INSTALL_ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL https://raw.githubusercontent.com/rodrigopg/whatsapp-mcp/main/install.sh -o /tmp/whatsapp-mcp-install.sh How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set up the WhatsApp bridge for this plugin. Follow the steps in order; do not skip ahead.
0. Detect existing accounts
Read ~/.claude.json and list any mcpServers keys starting with whatsapp (e.g. whatsapp, whatsapp-personal). Also check for existing install dirs: ~/.whatsapp-mcp*.
- None found → this is a first install. Skip ahead to step 1, use defaults (
~/.whatsapp-mcp, port 8080, server namewhatsapp). - One or more found → ask the user with AskUserQuestion:
- Question: "Found existing WhatsApp account(s):
<list the keys/dirs found>. What do you want to do?" - Options: "Add another account" / "Reconfigure/reinstall an existing one" / "Cancel"
- If add another account: ask a follow-up AskUserQuestion for a short label (e.g. "personal", "work"). Normalize it before using it in any path — lowercase, keep only
[a-z0-9-], collapse anything else (spaces, slashes, dots) to-. This becomes part of a real filesystem path (~/.whatsapp-mcp-<label>) and an MCP server key (whatsapp-<label>); a raw, unnormalized label (e.g. containing/or..) could resolve outside the intended directory or produce an invalid server name. Confirm the derived values (install dir, port, server name) with the user in the question itself (put them in the option descriptions) before proceeding. - If reconfigure: ask which existing account (list them), then run steps 1-6 against that account's existing dir/port instead of picking new ones.
- If cancel: stop here.
- Question: "Found existing WhatsApp account(s):
Carry the resolved INSTALL_DIR / BRIDGE_PORT / SERVER_NAME from this step through steps 1-6 below — every reference to "the installer" or "the MCP server" means for this specific account.
1. Check dependencies
Verify all three before installing anything. If any is missing, STOP — report which one and its install link. Do not partially install.
go version→ must be 1.25 or newer. Missing/old: https://go.dev/dl/uv --version→ any version. Missing: https://docs.astral.sh/uv/getting-started/installation/git --version→ any version. Missing: https://git-scm.com/downloads
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.
- 4d ago First seen · 139 lines · 22 tokens per session scan B cdab7d39fc06
setup is a command published in the GitHub repository rodrigopg/whatsapp-mcp (2 stars, last pushed 8d ago), licensed MIT. It adds 22 tokens to every session and 2,864 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
setup-video-vision
Interactive setup wizard for claude-video-vision — configure backend, whisper, frames, and verify dependencies.
review-claims
Analyze patent claims for 35 USC 112(b) compliance - antecedent basis, definiteness, and claim structure.
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-epo-formalities
Check patent application formalities for EPO compliance (Rules 42-49 EPC, EPO Guidelines Part A).
setup-patent-system
One-time setup for the patent creator system - downloads MPEP, builds search index, configures BigQuery.
typegen
Run Sanity TypeGen and troubleshoot type generation issues.