Borrowing it
Nothing to install: this file belongs to kevinrivm/vocero-crm. 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/kevinrivm/vocero-crm/main/.claude/skills/whatsapp-saas-meta-infra/SKILL.mdgit clone --depth 1 https://github.com/kevinrivm/vocero-crmWrote 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/kevinrivm/vocero-crm/whatsapp-saas-meta-infra)<a href="https://agentmods.dev/skills/kevinrivm/vocero-crm/whatsapp-saas-meta-infra"><img src="https://agentmods.dev/badge/skills/kevinrivm/vocero-crm/whatsapp-saas-meta-infra/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/kevinrivm/vocero-crm/whatsapp-saas-meta-infra"><img src="https://agentmods.dev/badge/skills/kevinrivm/vocero-crm/whatsapp-saas-meta-infra.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.00072 | $0.00454 |
| Opus 5.5 | $0.00029 | $0.00182 |
| Sonnet 5.5 | $0.00014 | $0.00091 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
whatsapp-saas-meta-infra 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.
What it actually says
WhatsApp SaaS Meta Infra
Use this skill to build the infrastructure layer of a WhatsApp SaaS, not just isolated API calls.
Workflow
- Identify the missing layer:
- Meta app configuration,
- Embedded Signup,
- token exchange,
- webhook ingestion,
- Supabase schema,
- message sending,
- or data deletion / deauthorize handling.
- Read the matching reference file:
references/architecture.mdfor the overall system designreferences/implementation-sequence.mdfor the recommended build orderreferences/meta-config.mdfor Meta app settings, callback URLs, and review-facing configreferences/api-blueprint.mdfor backend route contracts and responsibilitiesreferences/supabase-schema.mdfor SQL and data modeling
- Implement the missing layer in the user's stack.
- Validate the full chain, not only the isolated endpoint.
Guardrails
- Keep secrets server-side.
- Do not equate
acceptedwithdelivered. - Save enough identity data to support deauthorize callbacks later.
- Make webhooks idempotent and upsert by
message_id. - Revalidate local connection state against Meta when assets may have been deleted.
Minimum infrastructure standard
Treat these as the baseline:
- a real OAuth or Embedded Signup completion path,
- a backend code exchange endpoint,
- a webhook with GET verification and POST ingestion,
- Supabase tables for connections and message events,
- real message send actions,
- message status persistence,
- a deauthorize or data deletion path for compliance.
Output style
- Favor architecture and implementation order over scattered snippets.
- Show which part runs in frontend, backend, Meta, and database.
- When writing code, produce production-leaning defaults rather than demo-only code.
What ships with it
5 files 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.
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 · 54 lines · 72 tokens per session scan A 993ab6e9c67e
whatsapp-saas-meta-infra is a skill published in the GitHub repository kevinrivm/vocero-crm (419 stars, last pushed 4d ago), licensed MIT. It adds 72 tokens to every session and 454 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-30.
whatsapp-saas-meta-infra compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| whatsapp-saas-meta-infrakevinrivm/vocero-crm | Skill | 419 | 4d ago | MIT | A | 72 | Claude Code |
| mem0-oss-to-platformmem0ai/mem0 | Skill | 68k | 2d ago | Apache-2.0 | A | 217 | Claude Code, Codex |
| azure-mgmt-botservice-dotnetmicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 78 | Claude Code |
| fastapi-router-pymicrosoft/skills | Skill | 3.2k | yesterday | MIT | A | 46 | Claude Code |
| dev-runtimelangwatch/langwatch | Skill | 5.0k | yesterday | Apache-2.0 | A | 172 | Claude Code |
| api-designericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | A | 105 | Claude Code, Codex |
| migrate-segw-to-raparc-mcp/arc-1 | Skill | 252 | yesterday | MIT | A | 106 | Claude Code |