Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/halemogpa/whatsapp-mcp-server/deploy)<a href="https://agentmods.dev/skills/halemogpa/whatsapp-mcp-server/deploy"><img src="https://agentmods.dev/badge/skills/halemogpa/whatsapp-mcp-server/deploy.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.1 | $0.00061 | $0.00868 |
| Opus 5 | $0.00030 | $0.00434 |
| Sonnet 5 | $0.00012 | $0.00174 |
| Haiku 4.5 | $0.00006 | $0.00087 |
Grade B, and why
deploy 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 6d 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.
sudo nginx -t && sudo systemctl reload nginx Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS http://127.0.0.1:9100/health # {"ok": true} How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Deploying
This runs on a small VPS shared with other services. Typical free RAM is around
1.5GB. An unguarded docker compose build once OOM'd the box and took sshd down
with it. Two rules follow, and both have already been learned the hard way.
Before anything heavy
free -m
cat /proc/loadavg
Build
./deploy/safebuild <service> # mcp | bridge
safebuild preflights headroom and runs the build inside a memory-capped
systemd-run cgroup. Never docker compose build directly. An earlier
version of the wrapper capped the CLI rather than BuildKit, so the cap was a
no-op; if you touch it, verify the cap applies to the builder, not the client.
The bridge must build with -tags sqlite_fts5 or it crash-loops on the FTS5
virtual table.
Deploy
docker compose up -d
docker compose ps
curl -fsS http://127.0.0.1:9100/health # {"ok": true}
nginx
sudo nginx -t && sudo systemctl reload nginx
Reload, never restart. Other sites share this nginx. If nginx -t fails,
remove the symlink, reload, and stop. Do not iterate on a broken config with the
service down.
Never declare a 443 listener whose certificate is not already on disk. nginx will refuse to load and every site on the box goes with it.
Verify
# unauthenticated must be 401
curl -s -o /dev/null -w '%{http_code}\n' -X POST https://your-host/mcp \
-H 'Content-Type: application/json' -H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
bash tests/smoke.sh
Then confirm you did not push the box over:
docker stats --no-stream # any container near its mem_limit?
free -m # available dropping, swap climbing?
When it says "Up" but nothing works
Docker does not restart unhealthy containers, only exited ones. A container
can sit Up and broken indefinitely; one outage ran 18 hours while docker ps
looked fine. The autoheal sidecar handles this, and every container must carry
autoheal: "true" for it to apply.
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.
- 6d ago First seen · 104 lines · 61 tokens per session scan B 37e85f515db7
deploy is a skill published in the GitHub repository HalemoGPA/whatsapp-mcp-server (5 stars, last pushed 5d ago), licensed MIT. It adds 61 tokens to every session and 868 once invoked, about $0.0003 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 skills, from other repositories
testing-python
Write and evaluate effective Python tests using pytest. Use when writing tests, reviewing test code, debugging test failures, or improving test coverage. Covers test design, fixtures, parameterization, mocking, and async testing.
n8n-self-hosting
Deploy a production self-hosted n8n end-to-end to a fresh Linux VM over SSH, using Docker Compose behind a Caddy reverse proxy with automatic HTTPS. Use whenever the user wants to self-host, install, set up, provision, or deploy n8n on their own server/VPS/box (Hetzner, DigitalOcean, AWS EC2, bare metal, etc.) — in…
scrape-batch
Extract many known URLs in one polite, rate-limited pass. Use when the user hands over a list of links, a set of search hits to read in full, or asks to "scrape these pages" / "pull the content from all of them". Drives extract(action="batch"), which fans out with per-domain rate limiting and returns partial results…
compare
Structured comparison of 2+ alternatives with consistent criteria and decision matrix.
research-topic
Multi-step research orchestration. Use when user asks "research X", "summarize current state of Y", "what's the latest on Z", or compares approaches. Calls extract(action="agent") which searches the web, extracts top results, then synthesises a citation-preserving Markdown answer with one configured LLM.
temporal-query
Answer time-travel questions over stored memory — what was believed at a past point in time, when a belief changed, and what replaced it. Use when the user says "as of", "back in", "at the time", "history of", "timeline", "what did I think then", or asks why a current memory contradicts an older one.