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 sent-templatesgit 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/sent-templates)<a href="https://agentmods.dev/skills/sentdm/sent-plugin/sent-templates"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-templates/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/sent-templates"><img src="https://agentmods.dev/badge/skills/sentdm/sent-plugin/sent-templates.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.00080 | $0.00582 |
| Opus 5.5 | $0.00032 | $0.00233 |
| Sonnet 5.5 | $0.00016 | $0.00116 |
| Haiku 4.5 | $0.00008 | $0.00058 |
Grade A, and why
sent-templates 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 17d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sent Templates
Operate existing template records with templates.list, templates.get, templates.get_by_name, and templates.delete.
Establish connection and scope
Use client-managed OAuth 2.1/PKCE and never request or expose credentials. Surface the active organization and Sender Profile before deletion; use sent-account-readiness if the connection context does not expose both.
Avoid repeating template body text or sample data unnecessarily. Prefer template identifiers, names, languages, channels, categories, and statuses in summaries.
An organization grant may select an owned Sender Profile with the tool schema's optional profileId; omit it to act as the authenticated account. Validate ownership with sender_profiles.list or sender_profiles.get, and use the same selector for preflight reads, mutations, and follow-up reads. Profile grants cannot use this selector. Reauthorize for a different organization or a profile outside the grant. Never invent scope fields or request credentials.
Find and inspect templates
- Use
templates.listfor filtered discovery and pagination. - Use
templates.getfor an exact template identifier. - Use
templates.get_by_namewhen the user supplies a name. If a name can match more than one language, channel, or scope, present the candidates and resolve one exact record before continuing.
These tools inspect existing records. For authoring or classification, hand off to waba-template-author; for a tenant-facing creation experience, hand off to template-builder-ui.
Delete a template
- Resolve the request to one exact template.
- Fetch that target first with
templates.getortemplates.get_by_name. Never delete from a guessed identifier, broad filter, or stale list result. - Show a delete preview with the selected organization, Sender Profile, exact template identifier, name, language, channel, category, and status. State that deletion is destructive; do not repeat its body.
- Ask for explicit confirmation to delete this exact target. Earlier or general approval is not sufficient.
- Call
templates.deleteimmediately after confirmation. A change to target, scope, or record invalidates confirmation.
What ships with it
1 file 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.
- 17d ago Changed · +2 lines 82b029b83221
- 1mo ago First seen · 35 lines · 80 tokens per session scan A 81cea9d8688b
sent-templates is a skill published in the GitHub repository sentdm/sent-plugin (51 stars, last pushed yesterday), licensed MIT. It adds 80 tokens to every session and 582 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.
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.