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 agentmods add skills/fullstack-phoenix/saas_kit/html-emailsnpx skills add fullstack-phoenix/saas_kit --skill html-emailsgit clone --depth 1 https://github.com/fullstack-phoenix/saas_kitWhat 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 | $0.00042 | $0.01087 |
| Opus 5 | $0.00021 | $0.00544 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
Grade A, and why
html-emails 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTML Emails
Adds a Swoosh-based HTML email pipeline backed by Premailex. Emails are written
as HEEx templates wrapped in a shared layout, then premail/1 inlines the CSS
and generates a plain-text alternative. This improves deliverability and
consistent rendering in Gmail, Outlook, and Apple Mail. When authentication
or teams are present, it also swaps their notifiers over to the HTML pipeline.
When to use
- The app sends transactional email (confirmations, magic links, invites) and you want client-safe HTML with inline styles.
- You need a plain-text fallback generated automatically for every email.
- Don't reach for this if the app only sends raw text emails and rendering / deliverability isn't a concern — plain Swoosh is enough then.
Dependencies
- Requires: None.
- Recommended: None. Pairs naturally with
authentication(user notifier) andteams(invitation notifier) — if either is installed, this feature upgrades their email templates automatically.
Install
mix saaskit.feature.install html_emails
No install decisions. The installer adds the premailex dep, the mailer
helpers, the EmailHTML view, and the HTML/text layouts. Conditional
templates are generated only when their feature is present: user notifier +
auth email templates when authentication is installed, invitation notifier +
invite template when teams is installed.
What it generates
mix.exs— injects{:premailex, "~> 0.3.20"}intodeps.lib/my_app/mailer.ex— Swoosh mailer withbase_email/0,render_body/3(renders a HEEx template inside the layout),apply_layout/1, andpremail/1(inline CSS + plain-text body).lib/my_app_web/emails.ex—MyAppWeb.EmailHTML, embeds all templates underemails/*.htmlandemails/*.text.lib/my_app_web/emails/layout.html.heex+layout.text.heex— shared HTML and text layouts (reset CSS, preheader, footer).- When
authenticationis installed:lib/my_app/users/user_notifier.explususer_confirmation_instructions,user_magic_link_instructions, anduser_update_email_instructionsHEEx templates. - When
teamsis installed:lib/my_app/teams/invitation_notifier.explusemails/invite_user.html.heex.
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.
- yesterday First seen · 116 lines · 42 tokens per session scan A c270f75d9c8a
html-emails is a skill published in the GitHub repository fullstack-phoenix/saas_kit (2 stars, last pushed 2mo ago), licensed MIT. It adds 42 tokens to every session and 1,087 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…