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 sentdm/sent-plugin --skill waba-template-authorgit clone --depth 1 https://github.com/sentdm/sent-pluginWrote 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/sentdm/sent-plugin/waba-template-author)<a href="https://agentmods.dev/skills/sentdm/sent-plugin/waba-template-author"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/waba-template-author/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/sentdm/sent-plugin/waba-template-author"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/waba-template-author.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00056 | $0.01721 |
| Opus 5.5 | $0.00022 | $0.00688 |
| Sonnet 5.5 | $0.00011 | $0.00344 |
| Haiku 4.5 | $0.00006 | $0.00172 |
Grade A, and why
waba-template-author 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.
How it starts
The opening of the file, as written. The whole thing — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WhatsApp Template Author
Use this skill to turn a messaging intent into a valid body for POST /v3/templates, review it for WhatsApp policy risk, and explain the resulting lifecycle. Sent's template request is not Meta's Cloud API components[] shape.
Source precedence
When official sources disagree:
- Use the live Sent v3 OpenAPI for paths, request fields, and response shapes.
- Use the most specific current Sent guide for lifecycle and policy semantics.
- Preserve unknown provider values instead of forcing them into a closed enum.
The canonical references are the Sent template-definition guide, the v3 OpenAPI, and the webhook events reference. Do not use snapshot-era v2 examples.
Authoring workflow
1. Establish intent and category
Collect the business event, recipient expectation, requested action, language, channel overrides, and realistic sample values. Choose:
UTILITYfor a specific non-promotional transaction, account, or service event.MARKETINGfor promotions, offers, re-engagement, product discovery, or mixed promotional content.AUTHENTICATIONfor one-time verification codes and supported authentication flows.
If content mixes utility and promotion, classify it as marketing or split it. See references/waba-template-categories.md.
2. Build the Sent create request
POST /v3/templates accepts these top-level fields:
| Field | Requirement |
|---|---|
definition |
Required. Contains header, body, footer, buttons, optional definitionVersion, and optional authenticationConfig. |
category |
Optional: UTILITY, MARKETING, or AUTHENTICATION; omit for detection only when ambiguity is acceptable. |
language |
Optional locale such as en_US. |
creation_source |
Optional source string; from-api is the documented default. |
submit_for_review |
Optional Boolean; default false. Draft and validate before review. |
sandbox |
Optional Boolean for validation without side effects. |
What ships with it
7 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.
- 1mo ago First seen · 169 lines · 56 tokens per session scan A 7bc09641478b
waba-template-author is a skill published in the GitHub repository sentdm/sent-plugin (51 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,721 once invoked, about $0.0002 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.
Other skills, from other repositories
eddi-screens
How an EDDI Manager page is actually built — the app shell, the list-page pattern, detail pages, the config-editor chrome, wizards, and loading/empty/error states. Load before creating or restructuring a page.
eddi-ui
EDDI Manager's UI vocabulary — the existing primitives and shared components, their variant props, the brand tokens, and the styling rules. Load before writing or editing any component that renders.
eddi-data
EDDI Manager's data and plumbing conventions — routing, TanStack Query hooks, ApiClient, i18n propagation, MSW mocks and tests. Load when wiring a screen to real data or adding a route.
chatbot
Use when a support or sales bot on a live website must behave: persona/system prompt, grounding so it cannot invent prices or policy, jailbreak and injection defense, the human handoff, launch metrics and kill switch. NOT the agent loop or RAG index under it (that is building-agents), NOT a human answering one ticket…
connector-setup
Use when the user wants to add, connect, sign in to or fix an MCP connector (a server that gives you tools for an app such as GitHub, Linear or Notion).
research
Use when the user asks you to research, compare, fact-check or find current information, and the answer should come with sources.