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/update-saasmail/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/update-saasmail)<a href="https://agentmods.dev/skills/choyiny/saasmail/update-saasmail"><img src="https://agentmods.dev/badge/skills/choyiny/saasmail/update-saasmail.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
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.
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.00105 | $0.01375 |
| Opus 5 | $0.00053 | $0.00687 |
| Sonnet 5 | $0.00021 | $0.00275 |
| Haiku 4.5 | $0.00011 | $0.00137 |
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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update saasmail from upstream
Sync the local saasmail fork with the latest changes from choyiny/saasmail while preserving the user's local commits on top.
Why this exists
The user maintains a fork (or local clone) of https://github.com/choyiny/saasmail with their own commits layered on top. They want a one-shot command that:
- Grabs the latest upstream state.
- Replays their local commits on top (so local work stays at HEAD).
- Doesn't get stuck on conflicts they don't care about — when a hunk can't auto-merge, upstream wins.
Regular git pull creates merge commits and doesn't give conflict preference. Regular git rebase halts on conflicts. This skill wraps the right invocation.
Preconditions
Before running anything, confirm:
- Working directory is the saasmail repo (check for
wrangler.jsoncorwrangler.jsonc.exampleandworker/directory). If not, stop and tell the user. - The current branch is the one they want to update. Usually
main. If they're on a feature branch, ask which branch to rebase onto upstream/main before proceeding.
Steps
1. Ensure the upstream remote exists
Run git remote -v and check for an upstream entry pointing at https://github.com/choyiny/saasmail (allow .git suffix and [email protected]:choyiny/saasmail.git SSH form).
- If missing:
git remote add upstream https://github.com/choyiny/saasmail.git - If present but pointing elsewhere: stop and ask the user — don't silently rewrite a remote they configured deliberately.
2. Stash uncommitted changes if any
Run git status --porcelain. If there is any output (tracked modifications or staged changes):
git stash push -u -m "update-saasmail auto-stash"
Remember that you stashed, so you can restore at the end. Untracked-but-ignored files are fine to leave alone (-u covers untracked, not ignored).
3. Fetch upstream
git fetch upstream
4. Rebase onto upstream/main with upstream-wins conflict strategy
git rebase upstream/main -X ours
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.
- 8d ago First seen · 126 lines · 105 tokens per session scan A 82dcba5061ce
update-saasmail is a skill published in the GitHub repository choyiny/saasmail (247 stars, last pushed yesterday), licensed Apache-2.0. It adds 105 tokens to every session and 1,375 once invoked, about $0.0005 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.
Other skills, from other repositories
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.
agentify
Beta — Deploy the autonomous-repo feedback loop into a GitHub repo. Scaffolds the lane workflows, the runtime skill, and one config file as a reviewed PR, then prints the one-time identity/secret setup checklist. Turns a repo into one that triages incoming feedback into issues and prepares human-gated fix PRs. Use…
autonomous-repo
Runtime procedures for the autonomous-repo feedback loop — triage incoming feedback into GitHub issues, prepare human-gated fix PRs, and notify filers. Runs in the GitHub Actions lanes (headless) AND interactively. Reads autonomous-repo.config.yml for every product-specific value.
skills-update
USE WHEN: updating locked agent skills from skills-lock.json, refreshing upstream skill content, or running npx skills update for project skills. DO NOT USE WHEN: adding new skills (use npx skills add with explicit approval), running bare npx skills update without skill names, or updating project-local skills that are…
release-notes
Generate release notes from git history and CHANGELOG. Formats for GitHub Release, Slack, or email. Use before tagging a release.
github-create-issue
Create GitHub issues with proper formatting, labels, and details.