Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/sliamh11/Deusnpx agentmods add skills/sliamh11/deus/add-whatsappWrote 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/sliamh11/deus/add-whatsapp)<a href="https://agentmods.dev/skills/sliamh11/deus/add-whatsapp"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/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/sliamh11/deus/add-whatsapp"><img src="https://agentmods.dev/badge/skills/sliamh11/deus/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.00030 | $0.03274 |
| Opus 5 | $0.00015 | $0.01637 |
| Sonnet 5 | $0.00006 | $0.00655 |
| Haiku 4.5 | $0.00003 | $0.00327 |
Grade C, and why
add-whatsapp 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 9d 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.
rm -rf store/auth/ How it starts
The opening of the file, as written. The whole thing — 410 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add WhatsApp Channel
This skill adds WhatsApp support to Deus. It builds the local MCP packages, registers the channel, and guides through authentication.
IMPORTANT: Do NOT add git remotes, fetch from external repos, or install npm packages from the public registry during this skill. All channel code is already in the repo under packages/ and src/channels/.
Phase 1: Pre-flight
Recovery: If something goes wrong in Phase 1, simply re-run the skill from the beginning.
Check current state
Check if WhatsApp is already configured. If store/auth/ exists with credential files, skip to Phase 4 (Registration) or Phase 5 (Verify).
ls store/auth/creds.json 2>/dev/null && echo "WhatsApp auth exists" || echo "No WhatsApp auth"
Detect environment
Check whether the environment is headless (no display server):
[[ -z "$DISPLAY" && -z "$WAYLAND_DISPLAY" && "$OSTYPE" != darwin* ]] && echo "IS_HEADLESS=true" || echo "IS_HEADLESS=false"
Ask the user
Use AskUserQuestion to collect configuration. Adapt auth options based on environment:
If IS_HEADLESS=true AND not WSL → AskUserQuestion: How do you want to authenticate WhatsApp?
- Pairing code (Recommended) - Enter a numeric code on your phone (no camera needed, requires phone number)
- QR code in terminal - Displays QR code in the terminal (can be too small on some displays)
Otherwise (macOS, desktop Linux, Windows, or WSL) → AskUserQuestion: How do you want to authenticate WhatsApp?
- QR code in terminal (Recommended) - Displays QR code in the terminal
- Pairing code - Enter a numeric code on your phone (no camera needed, requires phone number)
If they chose pairing code:
AskUserQuestion: What is your phone number? (Include country code without +, e.g., 1234567890)
Phase 2: Build Local Packages
Recovery: If the build fails, fix the error and re-run from Phase 2. No need to redo Phase 1.
The WhatsApp channel is a local MCP server in packages/. Build the packages in order (core first, then whatsapp):
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.
- 9d ago First seen · 410 lines · 30 tokens per session scan C c7eccb21cd65
add-whatsapp is a skill published in the GitHub repository sliamh11/Deus (51 stars, last pushed 3d ago), licensed MIT. It adds 30 tokens to every session and 3,274 once invoked, about $0.0002 per session on Opus 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-08-30.
Other skills, from other repositories
memcord
Privacy-first, self-hosted chat memory for OpenClaw — save and recall conversation history across sessions without any cloud dependency.
roadmap-build
Build or repair a roadmap that agents can actually execute, not just read. Produces a single validated YAML source of truth, generated views, definitions of done with evidence kinds, a task pool linked on two axes, an idea intake queue, and three standing checks that keep it honest. Use when asked to "build a…
Research for Datacore
Automated research — source processing, podcast generation, and knowledge extraction.
GTD for Datacore
Getting Things Done — task capture, inbox processing, and org-mode management.
Outbox for Datacore
Content routing — archive to server, search archived content.
research-status
Check research queue counts, recent podcasts, knowledge base growth, and Readwise items.