What is event-driven-whatsapp-watches?

A skill for waiting for new messages in a specific WhatsApp chat and resuming the exact agent session that created the watch. It uses incoming events instead of repeatedly checking the chat.

Sending a WhatsApp message and waiting for a reply, monitoring one delegated chat, and continuing the original session when a matching incoming message arrives.

It avoids polling, which means making repeated checks when nothing has changed, and prevents a reply from being attached to the wrong conversation. It also handles message filtering and duplicate events.

event-driven-whatsapp-watches — Skill by dudu1111685/hermes

Install

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.

Any agent

npx skills add dudu1111685/hermes_mcps --skill event-driven-whatsapp-watches

Clone the repo

git clone --depth 1 https://github.com/dudu1111685/hermes_mcps

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dudu1111685/hermes_mcps/event-driven-whatsapp-watches/github.svg)](https://agentmods.dev/skills/dudu1111685/hermes_mcps/event-driven-whatsapp-watches)

Your own site

<a href="https://agentmods.dev/skills/dudu1111685/hermes_mcps/event-driven-whatsapp-watches"><img src="https://agentmods.dev/badge/skills/dudu1111685/hermes_mcps/event-driven-whatsapp-watches/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/dudu1111685/hermes_mcps/event-driven-whatsapp-watches"><img src="https://agentmods.dev/badge/skills/dudu1111685/hermes_mcps/event-driven-whatsapp-watches.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,580 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00031	$0.01580
Opus 5.5	$0.00012	$0.00632
Sonnet 5.5	$0.00006	$0.00316
Haiku 4.5	$0.00003	$0.00158

Measured 2mo ago against content hash 6e1c4a756163, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

event-driven-whatsapp-watches 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 2mo 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.

skills/event-driven-whatsapp-watches/SKILL.md · 139 lines

How it starts

The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Event-Driven WhatsApp Watches

Use this skill when the owner delegates a bounded WhatsApp conversation and wants Hermes to wake only when a matching incoming message arrives. This replaces frequent cron polling.

Required architecture

Hermes session calls waha_watch_chat
  -> native MCP boundary injects the current Hermes origin
  -> MCP stores watch + origin in a private shared store
  -> MCP preserves existing WAHA config and adds listener webhook
incoming WhatsApp message
  -> WAHA message + message.any webhooks
  -> listener normalizes GOWS JIDs, filters/deduplicates
  -> signed Hermes webhook V2 request
  -> webhook route validates origin/session identity
  -> gateway.wake.deliver_wake resumes exact opening session

The watch origin includes platform, chat ID/type, thread ID, user/profile/scope, durable session ID, and session key. A webhook event must not create a separate one-shot webhook conversation.

Tools

waha_send_text: sends a normal message without opening a watch.
waha_send_text_and_watch: sends a text and opens the watch in one race-safe call. Prefer this when waiting for a reply, so a fast reply cannot arrive between separate send and watch calls.
waha_watch_chat: opens a watch without sending any message and captures the opening Hermes session automatically.
waha_list_chat_watches: reads active/closed watches without secrets.
waha_update_chat_watch: changes bounded scope or expiry.
waha_close_chat_watch: explicitly closes the watch when the conversation is complete. Receiving one message never closes it automatically.

Never pass _hermesOrigin manually. Hermes injects it at the native MCP boundary.

Choose exactly the simplest matching mode:

Send only: waha_send_text or the normal humanized waha_reply; no watch is created.
Send and await replies: waha_send_text_and_watch; it creates the watch before sending and closes the new watch automatically if sending fails.
Watch only: waha_watch_chat; no outbound WhatsApp message is sent.
Stop: waha_close_chat_watch once the sender appears finished and the objective is clear.

Read the full file on GitHub · 139 lines

Changes

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.

2mo ago First seen · 139 lines · 31 tokens per session scan A 6e1c4a756163

Subscribe to this mod's changes

event-driven-whatsapp-watches is a skill published in the GitHub repository dudu1111685/hermes_mcps (6 stars, last pushed 2mo ago), licensed MIT. It adds 31 tokens to every session and 1,580 once invoked, about $0.0001 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-08-31.

event-driven-whatsapp-watches next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
event-driven-whatsapp-watchesdudu1111685/hermes_mcps	Skill	6	2mo ago	MIT	A	31	Claude Code, Codex
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code