Borrowing it
Nothing to install: this file belongs to choyiny/saasmail. 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/choyiny/saasmail/main/.claude/skills/create-saasmail-template/SKILL.mdgit clone --depth 1 https://github.com/choyiny/saasmailWrote 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/choyiny/saasmail/create-saasmail-template)<a href="https://agentmods.dev/skills/choyiny/saasmail/create-saasmail-template"><img src="https://agentmods.dev/badge/skills/choyiny/saasmail/create-saasmail-template.svg" alt="Measured on agentmods" 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.00000 | $0.04630 |
| Opus 5 | $0.00000 | $0.02315 |
| Sonnet 5 | $0.00000 | $0.00926 |
| Haiku 4.5 | $0.00000 | $0.00463 |
Grade A, and why
create-saasmail-template scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "$SAASMAIL_URL/api/email-templates" \ How it starts
The opening of the file, as written. The whole thing — 345 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating saasmail email templates
A template is a stored subject + bodyHtml pair rendered against caller-supplied
variables at send time. The renderer is Mustache-flavored but deliberately not
Mustache — it is a small, strict grammar in worker/src/lib/interpolate.ts, and
the differences are where mistakes happen.
Writing a template is really writing a contract: the tags you use decide which
variable names every future caller must supply, and a caller that misses one gets
a 400 instead of an email. Design that contract on purpose.
To send mail, enroll people in sequences, or manage API keys, use /use-saasmail
instead — this skill is about authoring the template itself.
Workflow
- Decide the contract first. For each piece of dynamic content, decide whether
the caller must always supply it (
{{key}}), might omit it ({{key?}}), or whether it is a list/conditional block ({{#key}}). Getting this wrong is the single most common failure — see "The send contract" below. - Write the markup. Email HTML, with tags from the grammar table.
- Create it via
POST /api/email-templates, or in the UI at/templates/new(which shows the detected variables and a live preview as you type). A template whose tags do not parse is rejected at write time with a diagnostic naming the offending tag — you cannot store a broken one. - Verify the contract with
GET /api/email-templates/{slug}/variables. Confirm thevariableslist matches what the caller actually passes — this is the check that catches a mistyped or accidentally-required name before it reaches production. - Test-send to a real address and look at the result in a mail client.
Never skip step 4. The analyzer's answer, not your reading of the template, is what the send path enforces.
The grammar
A tag is {{ or {{{, an optional sigil, a name, an optional ?, zero or more
|filter clauses, and a matching close of the same brace count.
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.
- 7d ago First seen · 345 lines · 0 tokens per session scan A 26f0abd0cef5
create-saasmail-template is a skill published in the GitHub repository choyiny/saasmail (247 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,630 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
supermemory
Supermemory is a state-of-the-art memory and context infrastructure for AI agents. Use this skill when building applications that need persistent memory, user personalization, long-term context retention, or semantic search across knowledge bases. It provides Memory API for learned user context, User Profiles for…
moemail
Use when an AI agent needs a temporary/disposable email address — for receiving verification emails, testing email integrations, or any task requiring a temporary inbox via the moemail CLI.
novu-manage-subscribers
Create, update, search, and delete subscribers in Novu. Manage topics for group-based notification targeting. Set subscriber credentials for push and chat channels. Use when managing notification recipients, creating subscriber records, organizing subscribers into topics, or configuring channel-specific credentials.
novu-trigger-notification
Trigger Novu notification workflows to send messages across email, SMS, push, chat, and in-app channels. Supports single triggers, bulk triggers, broadcast to all subscribers, topic-based targeting, and cancellation. Use when sending transactional notifications, alerts, or any event-driven messages.
add-provider
Add a new storage or service provider to the core package. Use when implementing a new backend for StorageService (e.g., a new database) or a new service provider (e.g., a new LLM backend).
novu-framework-integration
Build code-first notification workflows with @novu/framework. Use when defining workflows in TypeScript (Zod / JSON Schema / Class Validator), composing channel steps (email, SMS, push, chat, in-app) with action steps (delay, digest, custom), exposing Step Controls for non-technical teammates, rendering…