morning

morning is a command for Claude Code from rodrigopg/whatsapp-mcp. It costs 0 tokens per session (649 once invoked), scanned A, original, MIT.

A WhatsApp morning routine that reviews new messages, tracks open matters, prepares unsent follow-up drafts, and shows only items needing action today.

In plain words
What is it for?
It is for reviewing unread messages, drafting friendly chasers for overdue items, and displaying a dated morning summary with names, snippets, links, and reasons.
Why use it?
It turns scattered conversations into a short action list without sending messages on the user's behalf.

Command for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the whatsapp-mcp plugin — 7 commands shipped together

Good fit It is for reviewing unread messages, drafting friendly chasers for overdue items, and displaying a dated morning summary with names, snippets, links, and reasons.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/rodrigopg/whatsapp-mcp/morning
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.

Clone the repo
git clone --depth 1 https://github.com/rodrigopg/whatsapp-mcp

Made for: Claude Code.

Or install whatsapp-mcp, the plugin that ships this one along with the rest of its 7 commands.

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.

agentmods badge for morning

README.md
[![agentmods](https://agentmods.dev/badge/commands/rodrigopg/whatsapp-mcp/morning/github.svg)](https://agentmods.dev/commands/rodrigopg/whatsapp-mcp/morning)
Your own site
<a href="https://agentmods.dev/commands/rodrigopg/whatsapp-mcp/morning"><img src="https://agentmods.dev/badge/commands/rodrigopg/whatsapp-mcp/morning/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.

agentmods 80×15 button for morning

Your own site · 80×15
<a href="https://agentmods.dev/commands/rodrigopg/whatsapp-mcp/morning"><img src="https://agentmods.dev/badge/commands/rodrigopg/whatsapp-mcp/morning.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 649 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00649
Opus 5.5 $0.00000 $0.00260
Sonnet 5.5 $0.00000 $0.00130
Haiku 4.5 $0.00000 $0.00065

Measured 5d ago against content hash 4b296f6f2f08, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

morning 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 5d 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.

commands/morning.md · 38 lines

How it starts

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

Run the morning routine for the user. Nothing leaves this machine and no message is sent.

1. Review what is new

Do what /whats:triage does: review_next_messages, record or close matters following its rules, then mark_reviewed with next_cursor. Skip this step if there is nothing new.

2. Write chase drafts

Call list_matters with attention_only: true (same as_of as below). For each matter that the other person owes (owed_by: "other") and that has no pending draft in list_chase_drafts (state written), write a short, friendly message in the language and tone of that chat that asks about the snippet, and save it with create_chase_draft. This only saves a draft: nothing is sent.

3. Get the summary

Call morning_summary with as_of set to the current time with the user's UTC offset (for example 2026-10-12T07:00:00-03:00). The first call of the day builds the summary and stores it; calling again returns the same one.

4. Show it

One table, no running text, only what needs the user's action: name, time, snippet, link (when there is one), why it is there, and mark the uncertain ones. Keep the order you received (favorites, then who chased them or what they promised, then the rest).

  • If more is above zero, end with "N more": offer to show them and, if the user agrees, call morning_summary again with all: true.
  • Under the table, list the announcements as "closed because the other person confirmed": name, snippet, and offer reopen_matter if the user disagrees.
  • If nothing needs action, say so in one line.

5. Drafts waiting for the user

Show the drafts of the summary in a second table: draft id, name, the snippet it refers to and the text. For each one, ask the user: send as is, edit it, or discard it.

  • Call approve_chase_draft only after the user explicitly said to send that draft, passing exactly the text they approved (their edit, if they edited). That is the only way anything is sent.
  • If they discard it, call discard_chase_draft. If they say nothing, leave it: it shows up again tomorrow.
  • Never approve on your own, not even a draft that looks obvious, and never on a vague "ok" for several drafts at once.

Read the full file on GitHub · 38 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.

  1. 5d ago First seen · 38 lines · 0 tokens per session scan A 4b296f6f2f08

Subscribe to this mod's changes

morning is a command published in the GitHub repository rodrigopg/whatsapp-mcp (4 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 649 tokens. 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-10-12.