A release workflow for preparing and publishing a new software version. It checks milestone work, updates version references, creates a branch, writes release notes, validates the changes, and prepares a tag and pull request.

Use it when planning a release, increasing a version number, generating a changelog, or preparing the repository for publication.

It reduces the risk of missing unfinished issues, outdated version numbers, or required release files.

How s-morgan-jeffries/apple-mail-fast-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to s-morgan-jeffries/apple-mail-fast-mcp. 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/s-morgan-jeffries/apple-mail-fast-mcp/main/.claude/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/s-morgan-jeffries/apple-mail-fast-mcp

Made for: Claude Code.

Or install apple-mail-fast, the plugin that ships this one along with the rest of its 5 skills, 1 command, 3 hooks.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/s-morgan-jeffries/apple-mail-fast-mcp/release/github.svg)](https://agentmods.dev/skills/s-morgan-jeffries/apple-mail-fast-mcp/release)

Your own site

<a href="https://agentmods.dev/skills/s-morgan-jeffries/apple-mail-fast-mcp/release"><img src="https://agentmods.dev/badge/skills/s-morgan-jeffries/apple-mail-fast-mcp/release/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/s-morgan-jeffries/apple-mail-fast-mcp/release"><img src="https://agentmods.dev/badge/skills/s-morgan-jeffries/apple-mail-fast-mcp/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,370 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.

Model	Per session	Once invoked
Fable 5.1	$0.00049	$0.01370
Opus 5	$0.00024	$0.00685
Sonnet 5	$0.00010	$0.00274
Haiku 4.5	$0.00005	$0.00137

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

Security

Grade A, and why

release 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 11d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

release — 86% identical, 4 lines differ

.claude/skills/release/SKILL.md · 101 lines

How it starts

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

Release Workflow (12 Phases)

Phase 1: Milestone Check

List open milestones via gh api
Verify 0 open issues in target milestone
Stop if issues remain (ask user to move/close)

Phase 2: Version Number

Read current version from pyproject.toml (authoritative)
Milestone title = target version
Confirm with user

Phase 3: Create Release Branch

git checkout -b release/vX.Y.Z from main

Phase 4: Bump Version

Update ALL files (pyproject.toml is authoritative):

pyproject.toml — version = "X.Y.Z"
src/apple_mail_fast_mcp/__init__.py — __version__ = "X.Y.Z"
.claude/CLAUDE.md — **Version:** vX.Y.Z
README.md — all version references
mcpb/manifest.json — "version": "X.Y.Z" (the .mcpb bundle; check_version_sync.sh enforces it)
.claude-plugin/marketplace.json + .claude-plugin/plugin.json — every "version": "X.Y.Z" (the Claude Code plugin; check_version_sync.sh enforces all occurrences)

Phase 5: Generate CHANGELOG

Commits since last tag: git log v{prev}..HEAD --oneline
PRs since last release: gh pr list --state merged --search "merged:>YYYY-MM-DD"
Keep a Changelog format: ## [X.Y.Z] - YYYY-MM-DD
Categories: Added, Changed, Fixed, Removed

Phase 6: Test Coverage Review

Run coverage: make coverage
Compare against fail_under in pyproject.toml
Audit changed files for adequate coverage

Phase 7: Code Review

Launch superpowers:code-reviewer against cumulative diff
Critical issues block release

Phase 8: Documentation Review

README, CLAUDE.md, CHANGELOG, docs/**, tool docstrings, skills
The content-drift gate (check_docs.sh, Phase 9) automates the tool-set / removed-name / cross-ref / eval-description-sync parts; this phase is the human read for things it can't check (accuracy, tone, completeness).

Phase 8.5: Refresh derived artifacts (mandatory, #288)

Derived artifacts rot silently between releases — refresh them against the release commit so a stale snapshot can't ship:

make eval-descriptions — regenerate the blind-eval tool descriptions; commit if changed. (check_docs.sh also fails on drift here.)
Re-capture the benchmark baseline (#216): MAIL_TEST_MODE=true MAIL_TEST_ACCOUNT=<acct> uv run pytest tests/benchmarks/ --run-benchmark --capture-baseline (needs real Mail.app); commit the refreshed baseline.json.
Re-run the blind agent eval (#219) and refresh its scored snapshot (needs OPENROUTER_API_KEY); commit.

Read the full file on GitHub · 101 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.

11d ago First seen · 101 lines · 49 tokens per session scan A ec11df2307f8

Subscribe to this mod's changes

release is a skill published in the GitHub repository s-morgan-jeffries/apple-mail-fast-mcp (102 stars, last pushed yesterday), licensed MIT. It adds 49 tokens to every session and 1,370 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-30.

Git and workflow Releases apple-mail applescript claude email-automation macos mcp

release

Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…

sonichi/sutando · 68 tokens

publish-plugins

(project) Use when editing any file under skills/ or plugins/ to bump the plugin version and check the manifests.

vinta/hal-9000 · 26 tokens

release

Build, sign, notarize, and publish a new DroidProxy release. Use when the user wants to cut a release, merge a PR and ship it, or asks to build/notarize/publish. Covers the full pipeline: PR merge, version bump, swift build, code signing, Apple notarization, Sparkle appcast update, and GitHub release creation.

nikships/droidproxy · 80 tokens

apple-mail

Use this skill when the user wants to manage Apple Mail on macOS - reading, searching, sending, replying to, forwarding, and organizing emails and mailboxes. This skill provides access to Apple Mail through MCP tools.

sweetrb/apple-mail-mcp · 47 tokens

pr

Use when the user explicitly asks to push the current branch and open a PR, rewrite an open PR's body from its commits, or wait for CI and merge it.

vinta/hal-9000 · 35 tokens

confirmation-protocol

Foresay-derived confirmation workflow for email operations. Use this skill BEFORE executing archive-mail with vague filters, composeemail (sending mail), deleteemail/moveemail in bulk, or any operation that touches 5+ emails. Show user a structured preview of "what I understood" before taking action, achieving…

PsychQuant/che-apple-mail-mcp · 88 tokens

apple-mail-fast-mcp: Skill for Claude Code

Borrowing it

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

Copies of this mod

How it starts

Release Workflow (12 Phases)

Phase 1: Milestone Check

Phase 2: Version Number

Phase 3: Create Release Branch

Phase 4: Bump Version

Phase 5: Generate CHANGELOG

Phase 6: Test Coverage Review

Phase 7: Code Review

Phase 8: Documentation Review

Phase 8.5: Refresh derived artifacts (mandatory, #288)

What this file has done since we first saw it

Other skills, from other repositories

release

publish-plugins

release

apple-mail

pr

confirmation-protocol