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 m3taz-ahmed/ai-globals --skill whatsapp-smsgit clone --depth 1 https://github.com/m3taz-ahmed/ai-globalsWrote 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/m3taz-ahmed/ai-globals/whatsapp-sms)<a href="https://agentmods.dev/skills/m3taz-ahmed/ai-globals/whatsapp-sms"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/whatsapp-sms/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/m3taz-ahmed/ai-globals/whatsapp-sms"><img src="https://agentmods.dev/badge/skills/m3taz-ahmed/ai-globals/whatsapp-sms.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.00028 | $0.00543 |
| Opus 5.5 | $0.00011 | $0.00217 |
| Sonnet 5.5 | $0.00006 | $0.00109 |
| Haiku 4.5 | $0.00003 | $0.00054 |
Grade A, and why
whatsapp-sms 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.
What it actually says
[SKILL] whatsapp-sms [OBJ] Run high-intent WhatsApp and SMS programs — broadcasts, templates, and 1:1 flows — that respect opt-in and deliver strong ROI in MENA and emerging markets.
[RULES]
- [REQ] Opt-in first: no message without explicit, documented consent (double opt-in preferred). Align with
marketing-compliance(GDPR/CAN-SPAM equivalents, TCPA for SMS). - [REQ] Template approval: WhatsApp requires pre-approved templates per category (marketing/utility/auth). Draft compliant templates; avoid promotional language in utility.
- [CMD] Context7 IDs:
chatwoot/chatwoot(WhatsApp/SM channel, MIT),twentyhq/twenty(contact store),plausible/analytics(click tracking). - [REQ] Free-first: WhatsApp Business API via self-hosted Chatwoot (MIT) or free tier; Twilio free credit as parity; avoid vendor lock-in.
- [REQ] Segmentation: message by lifecycle stage (lead/customer/lapsed) and language. Never blast the whole list indiscriminately.
- [REQ] Arabic/RTL: Arabic WhatsApp needs RTL, proper diacritics optional, local sending windows (avoid late night GST), and Arabic opt-out keyword (مسح/إلغاء).
- [REQ] Frequency cap: max 2-4 msgs/week per user; honor immediate stop. Reduce churn via
client-retention. - [REQ] Measurement: delivery, read, reply, CTR, conversion. Feed
marketing-analytics. - [REQ] Automation: opt-in→welcome→sequence via
marketing-automation; human handoff for sales intent tob2b-cold-outreach. - [REQ] Approval gate: every broadcast requires explicit user approval (kernel write-gate).
[PROHIBIT]
- No WhatsApp/SMS without verified opt-in.
- No shared/sold phone numbers.
- No broadcast without user approval.
- No Arabic message without RTL + Arabic stop-word.
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.
- 1mo ago First seen · 39 lines · 28 tokens per session scan A 16b94ab5f4a3
whatsapp-sms is a skill published in the GitHub repository m3taz-ahmed/ai-globals (5 stars, last pushed 5d ago), licensed MIT. It adds 28 tokens to every session and 543 once invoked, about $0.0001 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-03.
Other skills, from other repositories
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
atmos-profiles
Atmos profiles: profile directories, --profile and ATMOSPROFILE activation, profile merge behavior, environment switching, and routing profile-specific auth/toolchain/config overrides.
webhook-management
Configure and validate CCAM webhook targets across supported chat, incident, automation, and generic providers. Use when listing provider requirements, creating or updating a target, scoping it to alert rules, sending a test notification, reviewing delivery history, or deleting a target.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.
deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…