agentmods.dev

saasmail: Skill for Claude Code

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

update-saasmail is a skill for Claude Code from choyiny/saasmail. It costs 121 tokens per session (2,097 once invoked), scanned A, original, Apache-2.0.

A procedure for updating a local copy or fork of the saasmail repository from its original GitHub repository. It keeps local commits on top of the newer upstream code and lets upstream changes win when conflicts cannot be merged automatically.

In plain words
What is it for?
It is for synchronising saasmail with choyiny/saasmail, checking the correct repository and branch, and rebasing local work onto the latest upstream version.
Why use it?
It avoids merge commits and prevents the update from stopping at conflicts that the user has chosen not to resolve manually.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

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 →

not rated 274repo +2 changed 9d ago A scan SkillSpector: warn 121 tokens original Apache-2.0
View source ↗ choyiny/saasmail choy.in
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/update-saasmail/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 update-saasmail

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/choyiny/saasmail/update-saasmail"><img src="https://agentmods.dev/badge/skills/choyiny/saasmail/update-saasmail.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 121 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,097 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 warn 7 Sept 2026
SkillSpector: 1 finding, 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 Excessive Agency · line 65
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00121 $0.02097
Opus 5.5 $0.00048 $0.00839
Sonnet 5.5 $0.00024 $0.00419
Haiku 4.5 $0.00012 $0.00210

Measured 9d ago against content hash 8c74fd2b5ea0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-saasmail 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/update-saasmail/SKILL.md · 157 lines

How it starts

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

Update saasmail

Two paths. Pick by how the instance was installed:

  • Installed with npx saasmail install (state in ~/.saasmail/<slug>/, or SAASMAIL_HOME): follow Upgrade from npm.
  • Installed from a clone (yarn saasmail install, state in the checkout's .saasmail/), or a fork or modified code the user keeps running from a clone: follow Sync a fork from upstream (below).

Ask if unsure. Never deploy from a clone with yarn deploy for an install the package owns.

Upgrade from npm

upgrade is npm-only; run it from any directory. Same rule as onboarding: you run the read-only plan, the user runs the apply in their own terminal, not with !, because the apply prints the setup code and credential prompts must stay out of this conversation.

  1. npx saasmail status [--name <name>] shows the recorded install, the running version and Latest on npm.

  2. Plan (read-only, safe from your shell):

    npx saasmail@latest upgrade --plan [--name <name>]

    Walk the user through it: new migrations, resources and secrets, and the plan digest. Say plainly that migrations cannot be undone; if a release is broken, the way back is the next release.

  3. It stops, changing nothing, in two cases:

    • Downgrade: the site runs a newer version than the package. Tell the user the version it names; never work around it.
    • Custom code: the running version is not a release (a modified fork, a dirty or diverged commit, or unknown). Ask explicitly whether they want to replace it. Only on a clear yes, the plan and apply get --replace-custom-code.

  4. Ask for an explicit yes, then give the user the apply command the plan printed (it ends with --expect-plan <digest> --yes) to run in their own terminal.

  5. If it fails, the message prints the command to continue. Ask for the error lines (never a Setup code: line), help fix the cause, and have them run npx saasmail@latest upgrade --resume [--name <name>] in their terminal. --resume continues even if the site is down. "The plan changed since it was reviewed" means something moved: plan again.

  6. Run npx saasmail status [--name <name>] yourself and confirm the running version matches Latest.

Read the full file on GitHub · 157 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 Changed · -8 lines · -9 tokens per session 8c74fd2b5ea0
  2. 18d ago Changed 5fb49d4958d7
  3. 19d ago Changed · +37 lines · +25 tokens per session ce7221368ea9
  4. 21d ago Changed · +2 lines 4492ae9c074f
  5. 2mo ago First seen · 126 lines · 105 tokens per session scan A 82dcba5061ce

Subscribe to this mod's changes

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

Git and workflowcloudflare-workersemailemail-mcpemail-mcp-servermcpsaas
Related

update-saasmail compared with skills from other repositories

update-saasmail next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-saasmailchoyiny/saasmailSkill2744d agoApache-2.0A121Claude Code
platform-deliveryheymegabyte/claude-skillsSkill221mo agononeA37Claude Code
moemailbeilunyang/moemailSkill2.8k2mo agoMITA37Claude Code, Codex
agentifytokencanopy/e2aSkill1984d agoApache-2.0A93Claude Code
autonomous-repotokencanopy/e2aSkill1984d agoApache-2.0A64Claude Code
skills-updatelouisbrulenaudet/monorepo-templateSkill195d agoApache-2.0A75Claude Code, Codex
changesetlouisbrulenaudet/monorepo-templateSkill195d agoApache-2.0A87Claude Code, Codex