Borrowing it
Nothing to install: this file belongs to HalemoGPA/whatsapp-mcp-server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HalemoGPA/whatsapp-mcp-server/main/.claude/skills/verify-wire-claim/SKILL.mdgit clone --depth 1 https://github.com/HalemoGPA/whatsapp-mcp-serverWrote 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/halemogpa/whatsapp-mcp-server/verify-wire-claim)<a href="https://agentmods.dev/skills/halemogpa/whatsapp-mcp-server/verify-wire-claim"><img src="https://agentmods.dev/badge/skills/halemogpa/whatsapp-mcp-server/verify-wire-claim/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/halemogpa/whatsapp-mcp-server/verify-wire-claim"><img src="https://agentmods.dev/badge/skills/halemogpa/whatsapp-mcp-server/verify-wire-claim.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.00068 | $0.00856 |
| Opus 5.5 | $0.00027 | $0.00342 |
| Sonnet 5.5 | $0.00014 | $0.00171 |
| Haiku 4.5 | $0.00007 | $0.00086 |
Grade A, and why
verify-wire-claim 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.
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verifying a claim about WhatsApp
WhatsApp enforces most of what you see client-side. The app bets that what people see is reality, and for almost everyone that bet is correct. It is not correct here, because this server reads the wire.
A rendering is evidence of what a client chose to draw. Nothing more.
Never accept these as evidence
| Source | Why not |
|---|---|
| A screenshot, or what the desktop app shows | Desktop and mobile enforce different things. A message once looked view-once on desktop for weeks while the inner flag was unset. |
| A comment in this repo | They rot. The two most confidently wrong statements in this codebase were comments that had been true when written. |
| A library's documentation | It describes the field's intent, not client behaviour. selectableOptionCount is documented as a maximum; no client enforces it above 1. |
| A tally or counter in the app | Five phones once showed five different poll tallies while the wire said one number. |
| "The endpoint returned success" | A poll vote returned Vote cast while the tally stayed at zero. |
Accept these
- The actual protobuf, with the field number.
- A test you ran, with its output.
- An observation from a real phone, on the receive path.
The procedure
-
Separate the three claims. "The field exists", "the server accepts it", and "the recipient's client honours it" are different, and a change can satisfy one and fail the others. Establish each on its own.
-
Test the send path. Call the tool. Capture the response.
-
Test the receive path on a real phone. This is the step people skip and it is where the bugs are. Sending through our own API exercises code that wraps and hashes locally and never decrypts or normalises. Two real bugs (all six poll-creation variants, and LID-vs-phone-number on votes) were found in minutes by a phone after the server-side tests passed clean.
-
Check the stored row. Read what actually landed in the message store, not what the tool said it wrote.
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 · 76 lines · 68 tokens per session scan A fa6dcf61abe2
verify-wire-claim is a skill published in the GitHub repository HalemoGPA/whatsapp-mcp-server (8 stars, last pushed 4d ago), licensed MIT. It adds 68 tokens to every session and 856 once invoked, about $0.0003 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.
verify-wire-claim compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| verify-wire-claimHalemoGPA/whatsapp-mcp-server | Skill | 8 | 4d ago | MIT | A | 68 | Claude Code |
| swagjmagar/swag-mcp | Skill | 7 | 4d ago | MIT | A | 118 | Claude Code |
| quantum-vqexi-zhao/OpenQuantum | Skill | 71 | yesterday | MIT | A | 53 | Claude Code, Codex |
| quantum-vqlsxi-zhao/OpenQuantum | Skill | 71 | yesterday | MIT | A | 56 | Claude Code, Codex |
| triaging-incidentsjschuller/mcp-server-servicenow | Skill | 27 | 2d ago | MIT | A | 89 | Claude Code |
| reviewing-update-setsjschuller/mcp-server-servicenow | Skill | 27 | 2d ago | MIT | A | 82 | Claude Code |
| reviewing-sla-definitionsjschuller/mcp-server-servicenow | Skill | 27 | 2d ago | MIT | A | 79 | Claude Code |