cos: Skill for Claude Code

.claude/skills/whatsapp-mcp-setup/SKILL.md

whatsapp-mcp-setup is a skill for Claude Code from philipyaz/cos. It costs 217 tokens per session (6,537 once invoked), scanned B, original, MIT.

A setup guide for connecting WhatsApp to Claude Code through two helper programs: one keeps the WhatsApp Web session running, and another makes WhatsApp actions available to Claude.

In plain words
What is it for?
It is for installing the WhatsApp bridge, configuring its ports and folders, supervising it with launchd on macOS, and connecting it to Claude clients.
Why use it?
It explains the separate parts and setup needed to get WhatsApp working on a new machine, including background services and their connections.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is philipyaz/cos's own configuration. It tells Claude Code how to work on cos itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything cos configures →

Reuse

Borrowing it

Nothing to install: this file belongs to philipyaz/cos. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/philipyaz/cos/main/.claude/skills/whatsapp-mcp-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/philipyaz/cos

Made for: Claude Code.

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-mcp-setup

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/philipyaz/cos/whatsapp-mcp-setup"><img src="https://agentmods.dev/badge/skills/philipyaz/cos/whatsapp-mcp-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 217 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,537 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 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.00217 $0.06537
Opus 5 $0.00109 $0.03268
Sonnet 5 $0.00043 $0.01307
Haiku 4.5 $0.00022 $0.00654

Measured 9d ago against content hash 91d24eb15ad1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

whatsapp-mcp-setup scanned grade B with 2 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 9d 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

grep -q '"whatsapp"' "$REPO_ROOT/.mcp.json" && echo ".mcp.json OK"

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

> bearer, so an **unauthenticated** `curl` returns **401, not 200** — a bare 200 is NOT the health
.claude/skills/whatsapp-mcp-setup/SKILL.md · 341 lines

How it starts

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

WhatsApp MCP setup (Go bridge sidecar :8010 + Python stdio MCP bridge :8006)

Why this exists / architecture

whatsapp-mcp is an external repo (the user's fork verygoodplugins/whatsapp-mcp) checked out outside this Cos repo at $WHATSAPP_MCP_DIR. It is two processes, and they register into Cos the same two ways the existing servers + sidecars do — getting this split wrong is the usual failure:

  • (a) The Go whatsmeow bridge (:8010)whatsapp-bridge/, a long-running HTTP daemon that holds the WhatsApp Web session and writes the SQLite stores. It is treated exactly like the search / guard SIDECARS: an HTTP backend, NOT a stdio MCP server, so it is NOT in .mcp.json. launchd supervises it under label com.chiefofstaff.mcp-whatsappbridge. (Its port is $WHATSAPP_GO_PORT, default 8010 — whatsmeow's own default is 8080, but that is commonly taken on a dev box, so cos pins it to 8010.)
  • (b) The Python stdio MCP (whatsapp-mcp-server/main.py) — a FastMCP stdio server (mcp.run(transport="stdio"), confirmed at main.py:396). It is exposed to Claude Code over HTTP via a supergateway + launchd BRIDGE on :8006 ($WHATSAPP_MCP_BRIDGE_PORT, label com.chiefofstaff.mcp-whatsapp, IN .mcp.json), and to Claude Cowork Desktop as a direct stdio command entry — identical to how mcp-bridge-setup wires board/openwhispr/etc.
Claude Code   ──HTTP──> localhost:8006/mcp ──supergateway(launchd)──> uv run main.py (Python stdio MCP)
                                                                          │  reads SQLite directly (messages.db)
                                                                          └──HTTP (bearer)──> Go bridge :8010 ──whatsmeow──> WhatsApp Web
Cowork Desktop ──spawns stdio directly──> uv run --directory $WHATSAPP_MCP_DIR/whatsapp-mcp-server main.py   (§6)
                          Go bridge :8010  =  launchd SIDECAR (com.chiefofstaff.mcp-whatsappbridge), NOT in .mcp.json   (§4)

Read the full file on GitHub · 341 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. 9d ago First seen · 341 lines · 217 tokens per session scan B 91d24eb15ad1

Subscribe to this mod's changes

whatsapp-mcp-setup is a skill published in the GitHub repository philipyaz/cos (4 stars, last pushed today), licensed MIT. It adds 217 tokens to every session and 6,537 once invoked, about $0.0011 per session on Opus 5. A static security scan graded it B with 2 findings (reads mcp configuration, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

wiki-lint

Health-check a wiki vault. Finds orphan pages (no inbound links), dead wikilinks (point to non-existent pages), missing frontmatter fields, stale claims, empty sections, and pages absent from catalog.md. Produces a structured report with severity tiers and proposes concrete fixes — but does not auto-apply them unless…

tboome33/obsidian-mcp-router · 119 tokens

opencode-plugin-idioms

Event hook payload shapes, session lifecycle timing, toast/TUI-route render boundaries, and child-session tagging conventions for OpenCode server (@opencode-ai/plugin) and TUI (@opencode-ai/plugin/tui) plugins, grounded in the vendored OpenCode source at references/opencode.

kagan-sh/kagan · 64 tokens

meta-sync-template

Interactive flow to propagate the reference (.template) vault's plugins, snippets, and root docs to one or more configured vaults. Reads the active router config, lists every vault with online status, flags vaults missing obsidian-local-rest-api upfront, lets the user pick all or a subset, and optionally re-clones…

tboome33/obsidian-mcp-router · 159 tokens

save

File the current Claude conversation (or a specific insight from it) as a structured wiki note. Auto-detects the right type (decision, answer, session-log, technique, ADR), writes appropriate frontmatter, places the file in the correct wiki folder, and updates catalog.md, journal.md, hot.md. Use when the user says…

tboome33/obsidian-mcp-router · 112 tokens

wiki-export

Export a vault's wiki either as a single portable file (llms.txt or llms-full.txt per the llmstxt.org standard) or as an OKF knowledge bundle (Google's Open Knowledge Format v0.1 — a shareable directory of markdown files any AI agent can consume). Use when the user says "export my wiki", "make an llms.txt", "share my…

tboome33/obsidian-mcp-router · 129 tokens

self-align

Adversarial self-audit of the Kagan repo through four lenses — code quality & YAGNI, security, spec alignment, docs/AGENTS.md freshness — each finding self-assessed and reported by severity and confidence for the developer to action. Use only when explicitly asked to self-align, audit, or health-check the codebase; it…

kagan-sh/kagan · 84 tokens