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 run-testsgit 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/run-tests)<a href="https://agentmods.dev/skills/malaccamaxgit/whatsapp-mcp-docker/run-tests"><img src="https://agentmods.dev/badge/skills/malaccamaxgit/whatsapp-mcp-docker/run-tests/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/run-tests"><img src="https://agentmods.dev/badge/skills/malaccamaxgit/whatsapp-mcp-docker/run-tests.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.00062 | $0.00592 |
| Opus 5.5 | $0.00025 | $0.00237 |
| Sonnet 5.5 | $0.00012 | $0.00118 |
| Haiku 4.5 | $0.00006 | $0.00059 |
Grade A, and why
run-tests 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Tests: WhatsApp MCP Docker
Run all tests inside tester-container. Never run npm test on the host. It
exits 1 because the Linux-only binary is missing. The _guard script also blocks
the run unless NODE_ENV=test.
Build the test container first
Required before the first run and after code changes:
docker compose --profile test build tester-container
Run all tests (unit + integration)
docker compose --profile test run --rm tester-container npm run test:all
Run a specific layer
# Unit tests only
docker compose --profile test run --rm tester-container npm run test:unit
# Integration tests only
docker compose --profile test run --rm tester-container npm run test:integration
# Single test file
docker compose --profile test run --rm tester-container npx tsx --test test/unit/crypto.test.ts
E2E tests (live WhatsApp session)
# Step 1: one-time auth (saves the session to .test-data/ on the host)
docker compose --profile test run --rm tester-container npm run test:auth
# Step 2: run live tests (read-only, no messages sent)
docker compose --profile test run --rm tester-container npm run test:e2e
Re-authenticate after about 20 days. The WhatsApp session expires at that point.
Lint and format (inside the container)
docker compose --profile test run --rm tester-container npm run lint
docker compose --profile test run --rm tester-container npm run format:check
Test layers at a glance
| Layer | Location | What it covers |
|---|---|---|
| Unit | test/unit/ |
Pure functions: phone, fuzzy-match, crypto, file-guard, permissions, audit, store |
| Integration | test/integration/ |
MCP protocol through a mock WhatsApp client and in-memory transport |
| E2E | test/e2e/ |
Live WhatsApp session (read-only) |
Notes
- The
npm run test:*scripts usetsx. Do not run tests withnode --test. It cannot resolve.tsfiles becausetsconfig.test.jsonsetsnoEmit: true. - Rebuild the test container after you change a
.tsfile, a.test.tsfile, orpackage.json.
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 · 72 lines · 62 tokens per session scan A 4f71107a66ec
run-tests is a skill published in the GitHub repository Malaccamaxgit/whatsapp-mcp-docker (1 stars, last pushed 10d ago), licensed Apache-2.0. It adds 62 tokens to every session and 592 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
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…
axiom-testing
Use when writing ANY test, debugging flaky tests, making tests faster, or choosing Swift Testing vs XCTest. Covers unit tests, UI tests, async testing, test architecture.
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
JMeter Load Testing
Load and performance testing skill using Apache JMeter, covering test plans, thread groups, assertions, listeners, timers, and distributed testing.
testing-patterns
Testing strategy: pyramid, AAA, mocks/fakes/stubs, flaky tests, coverage. Triggers: test, fixture, mock, stub, e2e, TDD, Playwright, Cypress, flaky, coverage, property-based.