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 skills add Malaccamaxgit/whatsapp-mcp-docker --skill troubleshoot-whatsappgit clone --depth 1 https://github.com/Malaccamaxgit/whatsapp-mcp-dockerWrote 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/malaccamaxgit/whatsapp-mcp-docker/troubleshoot-whatsapp)<a href="https://agentmods.dev/skills/malaccamaxgit/whatsapp-mcp-docker/troubleshoot-whatsapp"><img src="https://agentmods.dev/badge/skills/malaccamaxgit/whatsapp-mcp-docker/troubleshoot-whatsapp/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/malaccamaxgit/whatsapp-mcp-docker/troubleshoot-whatsapp"><img src="https://agentmods.dev/badge/skills/malaccamaxgit/whatsapp-mcp-docker/troubleshoot-whatsapp.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.00059 | $0.00943 |
| Opus 5.5 | $0.00024 | $0.00377 |
| Sonnet 5.5 | $0.00012 | $0.00189 |
| Haiku 4.5 | $0.00006 | $0.00094 |
Grade A, and why
troubleshoot-whatsapp 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 10d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshoot: WhatsApp MCP Docker
Quick reference
| Symptom | First thing to check |
|---|---|
| Container crashes on start | docker compose logs whatsapp-mcp-docker |
| WhatsApp not connected | Session expired. Run the authenticate tool again. |
| Auth 429 error | Rate limited by WhatsApp. Wait 10 to 15 minutes. |
| Auth 400 error | Pairing failed. The server falls back to a QR code, returned as an image in the tool response. |
| FTS5 search returns nothing | Messages may lack a text body. Check the messages table. |
| Fuzzy match picks the wrong contact | Pass the JID directly to bypass fuzzy matching. |
| Media download fails | Check that media_raw_json is stored for the message. |
| Container rebuilds slowly | Use an incremental build, not --no-cache, unless a source file changed. |
| Session lost after restart | Verify the volume exists: `docker volume ls |
Connection and session issues
WhatsApp not connected
The session may have expired. WhatsApp sessions last about 20 days without
activity. Run the authenticate MCP tool. If it fails, check the logs.
docker compose logs --tail 50 whatsapp-mcp-docker
Container exits immediately
docker compose logs whatsapp-mcp-docker
Look for these causes:
- binary resolution errors, such as
@whatsmeow-node/linux-x64-musl - missing environment variables
- volume permission errors
Session lost after a container restart
docker volume ls | Select-String whatsapp
If whatsapp-sessions is missing, the volumes were deleted. Run the setup again
and re-authenticate.
Authentication errors
| Code | Cause | Fix |
|---|---|---|
| 429 | WhatsApp rate limit | Wait 10 to 15 minutes before retrying |
| 400 | Pairing code rejected | The server auto-falls back to a QR code. Check the tool response for a base64 PNG image or a data:image/png;base64,... URI. Open the image in a browser. |
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.
- 10d ago First seen · 112 lines · 59 tokens per session scan A 05a7195590a1
troubleshoot-whatsapp is a skill published in the GitHub repository Malaccamaxgit/whatsapp-mcp-docker (1 stars, last pushed 10d ago), licensed Apache-2.0. It adds 59 tokens to every session and 943 once invoked, about $0.0002 per session on Opus 5.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-10-06.
Other skills, from other repositories
hermes-s6-container-supervision
Modify or debug s6 services in the Hermes Docker image.
smoke-test
Health smoke tests + auto-fix for gbrain installs (and OpenClaw services when present). Run after machine/container restarts or whenever something seems broken. Tests critical services, auto-fixes bounded local issues, and reports worker topology without starting daemons. Extensible via user-defined test scripts in…
competition-container-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is…
aks-troubleshooting
Debug live Azure Kubernetes Service (AKS) incidents with a read-only, evidence-first investigation. WHEN: pod crashes or Pending, CrashLoopBackOff, OOMKilled, ImagePullBackOff, node NotReady, DNS or ingress failure, connectivity timeout, network policy, SNAT exhaustion, node-pool scaling blocked by QuotaExceeded or…
meta-home-it-rescue
Use this meta-skill instead of answering directly when the user needs help with home, small-team, laptop, browser, printer, Docker, Git, network, UI, or deployment troubleshooting that benefits from multi-skill orchestration across symptom intake, environment capture, web lookup, and repair planning.
aks-gpu-inference
Diagnose Day-2 AKS GPU and KAITO incidents using profile-aware, read-only evidence. WHEN: 'Insufficient nvidia.com/gpu', GPU pod Pending, model-load OOM, DCGM/VRAM, KAITO Workspace not ready, or GPU autoscaling. DO NOT USE FOR: setup (airunway-aks-setup), non-GPU incidents (aks-troubleshooting), standalone VM quota…