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.
npx skills add TheSmokeDev/taskchad-os --skill whatsapp-bridgegit clone --depth 1 https://github.com/TheSmokeDev/taskchad-osWrote 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/thesmokedev/taskchad-os/whatsapp-bridge)<a href="https://agentmods.dev/skills/thesmokedev/taskchad-os/whatsapp-bridge"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/whatsapp-bridge/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/thesmokedev/taskchad-os/whatsapp-bridge"><img src="https://agentmods.dev/badge/skills/thesmokedev/taskchad-os/whatsapp-bridge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00063 | $0.00486 |
| Opus 5 | $0.00032 | $0.00243 |
| Sonnet 5 | $0.00013 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00049 |
Grade A, and why
whatsapp-bridge 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 7d 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.
What it actually says
WhatsApp Bridge
Wire WhatsApp into the existing chat interface as one more channel adapter. The
framework already abstracts Telegram/Slack/Discord (see .claude/sections/02_*);
this adds a WhatsApp adapter behind the same interface — it does not fork the
engine.
Provider
Use the WhatsApp Cloud API (Meta) or an equivalent gateway (e.g. Twilio for WhatsApp). Both deliver inbound messages via webhook and accept outbound sends via REST.
Required .env values:
WHATSAPP_PHONE_NUMBER_ID=
WHATSAPP_ACCESS_TOKEN=
WHATSAPP_VERIFY_TOKEN= # for webhook handshake
WHATSAPP_ALLOWED_NUMBERS= # comma-separated allowlist
Adapter contract
Implement the channel adapter to match the existing chat interface:
- Inbound — verify the webhook signature, drop senders not in
WHATSAPP_ALLOWED_NUMBERS, normalize the payload to the engine's message shape, and hand it to the router. - Outbound — render the engine's reply to WhatsApp's message format and POST it to the Cloud API.
Security
- Enforce
WHATSAPP_ALLOWED_NUMBERSon every inbound message — mirror theTELEGRAM_ALLOWED_USER_IDSallowlist pattern. Unknown senders are dropped, not answered. - Outbound sends are mutations: route them through the
chat.sendcapability gate with an audit trail. Never call the WhatsApp API directly from a tool. - Verify the webhook
X-Hub-Signature-256HMAC before trusting any payload.
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.
- 7d ago First seen · 57 lines · 63 tokens per session scan A 5cd53c131fdb
whatsapp-bridge is a skill published in the GitHub repository TheSmokeDev/taskchad-os (23 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 486 once invoked, about $0.0003 per session on Opus 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-03.
Other skills, from other repositories
secret-warn
Use when adding or tuning edit-time secret and code-injection guardrails or security hooks in Claude Code, or on mentions of secret detection, API key safety, hardcoded or leaked keys (AWS, Stripe, GCP, OpenAI, Anthropic, GitHub, Slack, JWT, PEM, .env), gitleaks-style or pre-commit secret scanning, false positives or…
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue"…
migrating-workflow-v4-to-v5
Upgrades an app from Workflow SDK 4.x to 5.0. Use when bumping the workflow / @workflow/ dependencies to v5, or when hitting removed v4 APIs — runStep, stepEntrypoint, workflow/internal/private, @workflow/core/private, writeToStream / closeStream / readFromStream on a World, world.steps.get without a runId…
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
trigger-realtime-and-frontend
Trigger.dev client/frontend surface: subscribe to runs in realtime (runs.subscribeToRun and the @trigger.dev/react-hooks hook useRealtimeRun), consume metadata and AI/text streams in React (useRealtimeStream), trigger tasks from the browser (useTaskTrigger, useRealtimeTaskTrigger), and mint scoped frontend credentials…
migrating-to-workflow-sdk
Migrates Temporal, Inngest, Trigger.dev, and AWS Step Functions workflows to the Workflow SDK. Use when porting Activities, Workers, Signals, step.run(), step.waitForEvent(), Trigger.dev tasks / wait.forToken / triggerAndWait, ASL JSON state machines, Task/Choice/Wait/Parallel states, task tokens, or child workflows.