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 razvangirgiz/wazap --skill whatsapp-inboxgit clone --depth 1 https://github.com/razvangirgiz/wazapWrote 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/razvangirgiz/wazap/whatsapp-inbox)<a href="https://agentmods.dev/skills/razvangirgiz/wazap/whatsapp-inbox"><img src="https://agentmods.dev/badge/skills/razvangirgiz/wazap/whatsapp-inbox/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/razvangirgiz/wazap/whatsapp-inbox"><img src="https://agentmods.dev/badge/skills/razvangirgiz/wazap/whatsapp-inbox.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.00053 | $0.01061 |
| Opus 5 | $0.00026 | $0.00531 |
| Sonnet 5 | $0.00011 | $0.00212 |
| Haiku 4.5 | $0.00005 | $0.00106 |
Grade A, and why
whatsapp-inbox 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 7d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WhatsApp inbox triage
Deliverable: a short, ranked list of what needs the user, with everything else compressed to one line. The user should finish reading in under a minute.
Collect
get_recent_messageswith the window the user implied (default 24h; "this week" = 168). If the result sayssync: "in_progress", wait 5 seconds and call it again once. Passinclude_previews: truewhen the window holds photos, so "[image]" becomes something you can describe; the first call over many photos takes a few seconds.list_chatswithfilter: "unread"to catch chats whose activity predates the window.get_unansweredfor who is still waiting: it returns only chats whose last word is theirs and asks for something, with the ask quoted. For "whom did I forget", passmin_age_hours: 48. Do not rebuild this fromlist_chats; the tool already skips conversations that ended in "ok, thanks".
Done collecting when every chat with unread messages appears in exactly one bucket below.
Triage
Sort each chat into one bucket:
- Needs you: a direct question to the user, a request, a mention of the user in a group (
senderis not the user and the text addresses them or quotes one of their messages), or money/dates/decisions awaiting them. - Probably handled by call: a Needs you candidate the user has since called. See Calls below.
- FYI: information with no ask. Shipping updates, "ok thanks", group chatter that reached a conclusion.
- Noise: promotions, broadcast lists, groups the user is muted in (
muted_untilin the future), forwards without a question.
Rank Needs you by: people over groups, older unanswered over newer, money and deadlines first.
Calls
A call after someone's ask is evidence the user dealt with it. For every Needs you candidate from an individual chat, look for a call message in that chat newer than the ask: the calls already in the window, or read_messages on that chat with types: ["call"]. A call whose call.outcome is answered moves the item to Probably handled by call, carrying when it was and how long it ran, and ending in a question, because the call may have been about something else:
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.
- 7d ago Changed 83be4d539b98
- 12d ago First seen · 67 lines · 53 tokens per session scan A f08c3de1a669
whatsapp-inbox is a skill published in the GitHub repository razvangirgiz/wazap (0 stars, last pushed today), licensed MIT. It adds 53 tokens to every session and 1,061 once invoked, about $0.0003 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
agentmail
Use your assigned AgentMail inbox to read email tasks, explicitly send or reply, and check delivery. Provided automatically by your inbox assignment.
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.