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 zavudev/zavu-skills --skill channel-setupgit clone --depth 1 https://github.com/zavudev/zavu-skillsWrote 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/zavudev/zavu-skills/channel-setup)<a href="https://agentmods.dev/skills/zavudev/zavu-skills/channel-setup"><img src="https://agentmods.dev/badge/skills/zavudev/zavu-skills/channel-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.
<a href="https://agentmods.dev/skills/zavudev/zavu-skills/channel-setup"><img src="https://agentmods.dev/badge/skills/zavudev/zavu-skills/channel-setup.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.00033 | $0.00974 |
| Opus 5 | $0.00016 | $0.00487 |
| Sonnet 5 | $0.00007 | $0.00195 |
| Haiku 4.5 | $0.00003 | $0.00097 |
Grade A, and why
channel-setup 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 today.
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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channel Setup
When to Use
Use this skill when wiring a freshly connected channel (WhatsApp, Telegram, Instagram, Messenger, email, phone number) into code, or when deciding which sender ID to pass to the API.
The two-layer model
Zavu has two objects that beginners often conflate:
| Layer | What it is | Where it lives |
|---|---|---|
| Account | The connection to a provider: a WhatsApp Business Account, a Facebook Page, an Instagram account, a Telegram bot, an email domain, a phone number | Connected in the dashboard (Accounts, Phone Numbers) or via partner invitations |
| Sender | The API handle that ROUTES accounts: what you pass as Zavu-Sender, what carries the webhook and the AI agent |
GET /v1/senders |
Billing: accounts are what you pay for (a WhatsApp account, a channel connection, a phone number). Senders are free — they are the view that groups your accounts under one sending identity.
Connecting always yields a ready sender. When an account is connected and no sender references it, Zavu creates one automatically, named after the account (the WhatsApp verified name, the Page name, the @username). The first sender of a project becomes the default. Partner-invitation connects have always worked this way; every connect surface now does.
Finding the sender to send from
GET /v1/senders is the answer to "what can I send with, and from where?". Each sender's channels array is the source of truth for capability — computed from its actual configuration, not inferred:
{
"id": "sender_12345",
"name": "Acme Store",
"channels": ["whatsapp", "sms", "voice"],
"isDefault": true
}
- An empty
channelsarray means the sender cannot send anything yet (a phone number alone does not enable SMS). - Omit
Zavu-Senderto use the project's default sender. - To target a specific one, pass its ID as a header inside the send params object:
'Zavu-Sender': "sender_12345".
Per-channel wiring
| You connected... | The sender... | Send with |
|---|---|---|
| WhatsApp (embedded signup or invitation) | auto-created, channels includes whatsapp once the account is active |
channel: "whatsapp" |
| Messenger Page / Instagram account | auto-created, named after the Page/@username | channel: "messenger" / "instagram" |
| Telegram bot | attached via POST /v1/senders/{senderId}/telegram (bot token from @BotFather) |
channel: "telegram" |
| Email domain (verified) | attach with emailAddress on sender create/update |
channel: "email" |
| Nothing yet (zero-setup start) | enableSmsOneway: true on POST /v1/senders or PATCH /v1/senders/{senderId} — no number, no credential, active immediately; recipients cannot reply |
channel: "sms_oneway" |
| Phone number | route it to a sender (PATCH /v1/phone-numbers/{id} with senderId) — that is what turns SMS on; add enableVoice for calls |
channel: "sms" / "voice" |
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.
- today Changed · +1 lines 9f6d119f71ed
- 10d ago First seen · 60 lines · 33 tokens per session scan A f9a364b6e29b
channel-setup is a skill published in the GitHub repository zavudev/zavu-skills (1 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 974 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.