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 agentmods add skills/steipete/agent-scripts/whatsappnpx skills add steipete/agent-scripts --skill whatsappgit clone --depth 1 https://github.com/steipete/agent-scriptsWhat 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 | $0.00022 | $0.00978 |
| Opus 5 | $0.00011 | $0.00489 |
| Sonnet 5 | $0.00004 | $0.00196 |
| Haiku 4.5 | $0.00002 | $0.00098 |
Grade A, and why
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 2d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use this as the first stop for WhatsApp work. Keep the source boundary sharp:
wacrawl: primary WhatsApp Desktop archive. Read-only, best local history, no network, no sending.wacli: linked-device accounts. Use for alt accounts, live sync, auth, sending, chat/group mutation, and WhatsApp Web protocol questions.
If the user names wacrawl or wacli repo work specifically, read that tool's own skill too.
Routing
- Primary WhatsApp reads/search/history: use
wacrawl. - Read/unread counts from WhatsApp Desktop: use
wacrawl; it has chat-level unread counts, not per-message read state. - Freshness-sensitive primary reads: check
wacrawl status; runwacrawl syncwhen asked or when current data matters. - Alt accounts such as
me,molty, or named stores: usewacli --account NAME. - Sending, reactions, presence, archive/pin/mute/mark-read, group/channel mutations: use
waclionly after explicit user intent. - Comparing coverage between sources: treat
wacrawlas Desktop archive truth for primary history, andwaclias linked-device/live coverage with protocol limits.
Safety
- Never send or mutate WhatsApp state unless explicitly requested.
- Prefer read-only
waclicommands for inspection: pass--read-onlyor setWACLI_READONLY=1. - Do not write into WhatsApp Desktop's app container.
- Do not edit
waclisession.dbdirectly. - Keep named
wacliaccounts isolated; do not merge stores. - Report source freshness, account name, and known gaps when answering from local stores.
Common Commands
Primary Archive
Freshness and status:
wacrawl status
wacrawl doctor
wacrawl sync
Unread triage:
wacrawl chats --limit 20
wacrawl unread --limit 20
wacrawl --json unread --limit 100
Search and slice messages:
wacrawl messages --after 2026-01-01 --limit 50
wacrawl messages --chat JID --asc --limit 100
wacrawl messages --has-media --limit 50
wacrawl --json search "query"
wacrawl search "query" --after 2026-01-01 --from-them
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.
- 2d ago First seen · 115 lines · 22 tokens per session scan A 6b127960523f
whatsapp is a skill published in the GitHub repository steipete/agent-scripts (6,590 stars, last pushed today), licensed MIT. It adds 22 tokens to every session and 978 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…