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/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/choyiny/saasmail/create-saasmail-template"><img src="https://agentmods.dev/badge/skills/choyiny/saasmail/create-saasmail-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 253 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Prompt Injection · line 308 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 311 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 312 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 313 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 315 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.5 | $0.00000 | $0.01852 |
| Sonnet 5.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 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.
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.
- 2mo 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 (274 stars, last pushed 4d 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.
create-saasmail-template compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| create-saasmail-templatechoyiny/saasmail | Skill | 274 | 4d ago | Apache-2.0 | A | 0 | Claude Code |
| cf-integrations-referenceheymegabyte/claude-skills | Skill | 22 | 1mo ago | none | A | 53 | Claude Code |
| moemailbeilunyang/moemail | Skill | 2.8k | 2mo ago | MIT | A | 37 | Claude Code, Codex |
| add-providercyanheads/mcp-ts-core | Skill | 153 | yesterday | Apache-2.0 | A | 47 | Claude Code, Codex |
| email-connectorericrisco/rsc-harness | Skill | 503 | 2d ago | MIT | B | 83 | Claude Code, Codex |
| e2a-doctortokencanopy/e2a | Skill | 198 | 4d ago | Apache-2.0 | A | 69 | Claude Code |
| e2a-integratetokencanopy/e2a | Skill | 198 | 4d ago | Apache-2.0 | A | 68 | Claude Code |