Borrowing it
Nothing to install: this file belongs to fmbenhassine/chessclaw. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fmbenhassine/chessclaw/main/.codex/skills/add-whatsapp/SKILL.mdgit clone --depth 1 https://github.com/fmbenhassine/chessclawWrote 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/fmbenhassine/chessclaw/add-whatsapp)<a href="https://agentmods.dev/skills/fmbenhassine/chessclaw/add-whatsapp"><img src="https://agentmods.dev/badge/skills/fmbenhassine/chessclaw/add-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/fmbenhassine/chessclaw/add-whatsapp"><img src="https://agentmods.dev/badge/skills/fmbenhassine/chessclaw/add-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.00042 | $0.02013 |
| Opus 5 | $0.00021 | $0.01007 |
| Sonnet 5 | $0.00008 | $0.00403 |
| Haiku 4.5 | $0.00004 | $0.00201 |
Grade A, and why
add-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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Replace Current Transport With WhatsApp
This skill updates ChessClaw so that WhatsApp is the only live messaging transport.
It is intended for the current single-channel architecture. Use it when the user wants to:
- keep the existing WhatsApp runtime and set it up cleanly
- switch a fork back from Telegram or another transport to WhatsApp
- make WhatsApp the only assistant channel
Do not preserve any old multi-channel or multi-chat design. The target architecture is:
- one direct WhatsApp chat as the assistant channel
- one assistant workspace
- one persistent session
- no parallel Telegram or secondary transport runtime
What This Skill Should Do
When executed, this skill should transform or confirm the codebase so that:
- WhatsApp is the only live messaging transport
- The single-channel runtime stays intact
- The assistant still uses:
assistant/AGENTS.mdassistant/data/session/.codex/data/ipc/
- The request lifecycle remains:
- transport ingest
- SQLite persistence
- single message queue
- Apple container
- Codex thread
- transport reply
Do not reintroduce:
- group registration
registered_groups- per-chat folders
- per-chat sessions
- per-chat queueing
- chat privilege models
Questions To Ask
Before editing code, ask the user:
- Should the assistant use the authenticated WhatsApp self-chat, or one explicit direct 1:1 chat JID?
- If not the self-chat, what exact WhatsApp JID should be used?
Prerequisites
1. Install WhatsApp Dependencies
If the repo does not already include the WhatsApp transport dependencies, install them:
npm install @whiskeysockets/baileys qrcode-terminal
npm install -D @types/qrcode-terminal
If the current fork already has these dependencies, do not duplicate or replace them.
2. Authenticate With WhatsApp
Tell the user:
I need you to authenticate ChessClaw with WhatsApp.
- Run
npm run auth- Open WhatsApp on your phone
- Go to Settings -> Linked Devices -> Link a Device
- Scan the QR code shown in the terminal
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 309 lines · 42 tokens per session scan A 38d943d3ad88
add-whatsapp is a skill published in the GitHub repository fmbenhassine/chessclaw (5 stars, last pushed 5mo ago), licensed MIT. It adds 42 tokens to every session and 2,013 once invoked, about $0.0002 per session on Opus 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-08-31.
Other skills, from other repositories
add-dial-tool
Give chosen NanoClaw agents a real phone number as a container tool — the dial CLI baked into the agent image plus OneCLI credential injection for api.getdial.ai, scoped per agent, so the agents you pick can send SMS, place AI voice calls, and receive verification codes from inside the sandbox. Independent of the Dial…
add-signal
Add Signal channel integration via signal-cli device-link. Native adapter — no Chat SDK bridge.
add-telegram
Add Telegram channel integration via Chat SDK.
add-matrix
Add Matrix channel integration via Chat SDK. Works with any Matrix homeserver.
add-gchat
Add Google Chat channel integration via Chat SDK.
onecli-gateway
OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. You MUST use this skill when the user asks you to read emails, check calendar, access GitHub repos, create issues, check Stripe payments, or interact with ANY external service or API. Do NOT use browser extensions or OAuth CLI…