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 test-troubleshootinggit 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/test-troubleshooting)<a href="https://agentmods.dev/skills/malaccamaxgit/whatsapp-mcp-docker/test-troubleshooting"><img src="https://agentmods.dev/badge/skills/malaccamaxgit/whatsapp-mcp-docker/test-troubleshooting/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/test-troubleshooting"><img src="https://agentmods.dev/badge/skills/malaccamaxgit/whatsapp-mcp-docker/test-troubleshooting.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.01570 |
| Opus 5.5 | $0.00024 | $0.00628 |
| Sonnet 5.5 | $0.00012 | $0.00314 |
| Haiku 4.5 | $0.00006 | $0.00157 |
Grade C, and why
test-troubleshooting scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
docker compose run --rm tester-container rm -rf node_modules/.vite How it starts
The opening of the file, as written. The whole thing — 204 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Container Troubleshooting: WhatsApp MCP Docker
Common issues and solutions
Issue 1: the test container uses a cached build (files not updated)
Symptoms:
- You added or modified a file, for example
src/utils/timezone.ts. - The test container build says
CACHEDfor all layers. - Tests fail with
Cannot find module, or show old behavior. - The file exists on the host but not in the container.
Example error:
Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/app/src/utils/timezone.ts'
Root cause: the Docker build cache does not detect some file changes. This happens when you add a file after a layer is cached, or when a modification time does not change.
Solution, in order of preference:
# Option A: force a rebuild of the test image
docker rmi whatsapp-mcp-docker-tester-container:latest
docker compose --profile test build tester-container
# Option B: touch the file to invalidate the cache, then rebuild
(Get-Content src/utils/timezone.ts) | Set-Content src/utils/timezone.ts
docker compose --profile test build tester-container
# Option C: full rebuild, slow
docker compose --profile test build --no-cache tester-container
Prevention: check the build output for the COPY src/ layer. If it says
CACHED, the container has old files. After you add files, remove the image and
rebuild.
Issue 2: tests work with npm run test:unit but fail with node --test
Symptoms:
# Works
docker compose run --rm tester-container npm run test:unit
# Fails
docker compose run --rm tester-container node --test test/unit/timezone.test.ts
Error: Cannot find module '/app/src/utils/phone.ts'.
Root cause: npm run test:* uses tsx. tsx resolves .ts files directly.
node --test expects compiled output. tsconfig.test.json sets noEmit: true,
so no compiled test output exists.
Solution: always use tsx for tests.
# Correct
docker compose run --rm tester-container npm run test:unit
docker compose run --rm tester-container npx tsx --test test/unit/*.test.ts
# Wrong
docker compose run --rm tester-container node --test test/unit/timezone.test.ts
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 · 204 lines · 59 tokens per session scan C 04edc8de3235
test-troubleshooting 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 1,570 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-06.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.