whatsapp-formatting

whatsapp-formatting is a skill for Claude Code, Codex from taslim/nanoclaw-gws-ea. It costs 48 tokens per session (830 once invoked), scanned A, original, MIT.

A formatting guide for messages sent through WhatsApp, including real user mentions. WhatsApp is a messaging service, and its mention syntax uses a person's phone-number digits rather than their display name.

In plain words
What is it for?
Use it to format replies in one-to-one or group WhatsApp chats and tag users so their names become clickable and they receive a notification.
Why use it?
It prevents mentions from appearing as ordinary text without notifying the person. It also helps identify when a conversation is actually taking place in WhatsApp.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to format replies in one-to-one or group WhatsApp chats and tag users so their names become clickable and they receive a notification.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/taslim/nanoclaw-gws-ea/whatsapp-formatting
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 taslim/nanoclaw-gws-ea --skill whatsapp-formatting
Clone the repo
git clone --depth 1 https://github.com/taslim/nanoclaw-gws-ea

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.

agentmods badge for whatsapp-formatting

README.md
[![agentmods](https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/whatsapp-formatting/github.svg)](https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/whatsapp-formatting)
Your own site
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/whatsapp-formatting"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/whatsapp-formatting/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 whatsapp-formatting

Your own site · 80×15
<a href="https://agentmods.dev/skills/taslim/nanoclaw-gws-ea/whatsapp-formatting"><img src="https://agentmods.dev/badge/skills/taslim/nanoclaw-gws-ea/whatsapp-formatting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 830 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.00048 $0.00830
Opus 5.5 $0.00019 $0.00332
Sonnet 5.5 $0.00010 $0.00166
Haiku 4.5 $0.00005 $0.00083

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

Security

Grade A, and why

whatsapp-formatting 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 1mo 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.

container/skills/whatsapp-formatting/SKILL.md · 62 lines

How it starts

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

WhatsApp Message Formatting

WhatsApp uses its own lightweight markup and a phone-number-based mention syntax. The host's WhatsApp adapter (Baileys) handles markdown conversion automatically, but mentions are only protocol-level mentions if you use the right syntax — otherwise they render as plain text and don't notify the recipient.

How to detect WhatsApp context

You're in a WhatsApp conversation when any of these are true:

  • The chat JID / platform id ends with @s.whatsapp.net (1-on-1 DM)
  • The chat JID / platform id ends with @g.us (group)
  • Your inbound message metadata has chatJid matching the above

Mentions — the important part

To tag a user so their name appears bold and clickable in WhatsApp and they get a push notification, write the @ followed by their phone number digits (no +, no spaces, no display name):

@15551234567 can you confirm?

The adapter scans your outgoing text for @<digits> (5–15 digits, optional leading + is stripped) and tells WhatsApp to render them as real mention tags.

The sender's phone JID is always in your inbound message metadata. When a user writes to you, inbound content.sender looks like [email protected]. The part before the @ is exactly what you put after @ when tagging them back.

Wrong vs right

You write What recipients see
@Adam can you... Plain text @Adam. No tag, no notification.
@15551234567 can you... Bold/blue @Adam (or whatever name they're saved as), notification fires.
@+15551234567 ... Same as above — adapter strips the +.

Picking who to tag

  • In a DM, there's no real need to tag the recipient (they already see every message), but tagging still works if you want emphasis.
  • In a group, look at the participants / inbound content.sender to find the JID of the person you mean. Don't guess from display names — pushNames can collide and are not reliable.
  • If you don't know the JID, just refer to the person by name in plain prose. Don't write @<name> — it won't tag and it will look like a tag that failed.

Read the full file on GitHub · 62 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 1mo ago First seen · 62 lines · 48 tokens per session scan A d20ec7024c8c

Subscribe to this mod's changes

whatsapp-formatting is a skill published in the GitHub repository taslim/nanoclaw-gws-ea (11 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 830 once invoked, about $0.0002 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-09-18.