saasmail: Skill for Claude Code

.claude/skills/saasmail-onboarding/SKILL.md

saasmail-onboarding is a skill for Claude Code from choyiny/saasmail. It costs 84 tokens per session (4,111 once invoked), scanned A, original, Apache-2.0.

An interactive setup guide for deploying a self-hosted saasmail email service to Cloudflare.

In plain words
What is it for?
Use it when setting up, deploying, or configuring saasmail in a live Cloudflare account.
Why use it?
It helps configure the required Cloudflare resources, domains, email provider, and deployment steps without treating local development as deployment.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: positional $N argument.

This is choyiny/saasmail's own configuration. It tells Claude Code how to work on saasmail itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything saasmail configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/choyiny/saasmail/main/.claude/skills/saasmail-onboarding/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/choyiny/saasmail

Made for: Claude Code.

Wrote 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.

agentmods badge for saasmail-onboarding

README.md
[![agentmods](https://agentmods.dev/badge/skills/choyiny/saasmail/saasmail-onboarding/github.svg)](https://agentmods.dev/skills/choyiny/saasmail/saasmail-onboarding)
Your own site
<a href="https://agentmods.dev/skills/choyiny/saasmail/saasmail-onboarding"><img src="https://agentmods.dev/badge/skills/choyiny/saasmail/saasmail-onboarding/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.

agentmods 80×15 button for saasmail-onboarding

Your own site · 80×15
<a href="https://agentmods.dev/skills/choyiny/saasmail/saasmail-onboarding"><img src="https://agentmods.dev/badge/skills/choyiny/saasmail/saasmail-onboarding.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 84 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,111 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00084 $0.04111
Opus 5 $0.00042 $0.02056
Sonnet 5 $0.00017 $0.00822
Haiku 4.5 $0.00008 $0.00411

Measured 9d ago against content hash 9486afee3959, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

saasmail-onboarding 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 9d 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.

.claude/skills/saasmail-onboarding/SKILL.md · 331 lines

How it starts

The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.

saasmail Onboarding Wizard

Guide the user through deploying a production saasmail instance to their Cloudflare account. This wizard is deployment-only — it does not set up local development. Every step targets the user's live Cloudflare environment.

Before You Start

Read wrangler.jsonc.example in the project root so you know the exact shape of the config that will be filled in. It is your source of truth for which resources and bindings are required.

What the user is signing up for

Set expectations up front, so the user knows what they're committing to:

  • ~30–40 minutes total; most of the wait is DNS propagation, not typing.
  • Two decisions: which domains will be used, and which outbound email provider (Cloudflare Email Sending, Resend, Bavimail, or Postmark).
  • Three manual Cloudflare-dashboard steps (Email Routing per inbound domain, Email Service per send-from domain, and checking the deployed worker).
  • Cost: a Cloudflare Workers Paid plan (~$5/mo) is required. saasmail uses Queues, which aren't on the free plan. Email Routing is free; Cloudflare Email Sending is usage-based.

Tell the user all of this before touching anything, so they can back out cheaply.

Preflight Checkpoints (hard gates)

Confirm each of these explicitly with the user — ask, don't assume. If any answer is "no", stop and help them resolve it before continuing. These exist because every later step assumes them, and a half-configured Cloudflare account is annoying to clean up.

Checkpoint 1 — Do you own a domain?

Ask: "Do you already own a domain you want to use for saasmail?"

  • No → Stop. Tell them to buy one (Cloudflare Registrar, Namecheap, etc.) and come back. A single domain can cover all three roles; split domains are also fine.

Checkpoint 2 — Is that domain on Cloudflare?

Ask: "Are the domain's nameservers pointing to Cloudflare (the domain is an active Cloudflare zone)?"

  • No → Stop. Instruct them to open the Cloudflare dashboard → Add a Site, then switch nameservers at their registrar to the ones Cloudflare provides. Propagation can take up to a few hours. Both Email Routing and custom_domain worker routes require the zone to live on Cloudflare.

Read the full file on GitHub · 331 lines

Changes

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.

  1. 9d ago First seen · 331 lines · 84 tokens per session scan A 9486afee3959

Subscribe to this mod's changes

saasmail-onboarding is a skill published in the GitHub repository choyiny/saasmail (247 stars, last pushed 2d ago), licensed Apache-2.0. It adds 84 tokens to every session and 4,111 once invoked, about $0.0004 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-30.