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

.claude/skills/integration-testing/SKILL.md

integration-testing is a skill for Claude Code from s-morgan-jeffries/apple-mail-fast-mcp. It costs 52 tokens per session (1,038 once invoked), scanned A, original, MIT.

A guide for testing software against a real Apple Mail installation, Apple's built-in email application. It explains when mocked tests are insufficient and describes unit, integration, and end-to-end testing.

In plain words
What is it for?
Use it when setting up or debugging real-Mail tests, adding AppleScript operations, or investigating behavior that mocked tests do not explain.
Why use it?
Tests that replace Apple Mail with a mock cannot reveal real AppleScript errors, Mail.app behavior, account differences, or timeout problems.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is s-morgan-jeffries/apple-mail-fast-mcp's own configuration. It tells Claude Code how to work on apple-mail-fast-mcp 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 apple-mail-fast-mcp configures →

Part of the apple-mail-fast plugin — 5 skills, 1 command, 3 hooks shipped together

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/integration-testing/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.

agentmods badge for integration-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/s-morgan-jeffries/apple-mail-fast-mcp/integration-testing/github.svg)](https://agentmods.dev/skills/s-morgan-jeffries/apple-mail-fast-mcp/integration-testing)
Your own site
<a href="https://agentmods.dev/skills/s-morgan-jeffries/apple-mail-fast-mcp/integration-testing"><img src="https://agentmods.dev/badge/skills/s-morgan-jeffries/apple-mail-fast-mcp/integration-testing/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 integration-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/s-morgan-jeffries/apple-mail-fast-mcp/integration-testing"><img src="https://agentmods.dev/badge/skills/s-morgan-jeffries/apple-mail-fast-mcp/integration-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 52 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,038 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.00052 $0.01038
Opus 5 $0.00026 $0.00519
Sonnet 5 $0.00010 $0.00208
Haiku 4.5 $0.00005 $0.00104

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

Security

Grade A, and why

integration-testing 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

2 near-identical copies found in the catalogue:

.claude/skills/integration-testing/SKILL.md · 135 lines

How it starts

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

Apple Mail Integration Testing

Why Integration Tests Matter

Unit tests mock _run_applescript() and test Python logic only. They CANNOT catch:

  • AppleScript syntax errors
  • Variable naming conflicts in AppleScript
  • Mail.app API behavior differences between versions
  • Silently-dropped record keys from NSJSONSerialization (e.g., name, id, size selector collisions)
  • Gmail-specific behavior differences
  • Timeout issues with real mailbox sizes

The OmniFocus project's story: A variable naming typo went undetected by 400+ unit tests because they all mocked the AppleScript boundary. Only integration tests against the real app caught it. This lesson applies equally to Apple Mail.

Three-Tier Testing Strategy

Tier Speed What it catches When to run
Unit (mocked) ~1s, 99 tests Python logic, parsing, validation Every change
Integration (real) ~30s AppleScript bugs, Mail.app quirks New AppleScript code
E2E (full MCP) ~30s Tool registration, parameter passing New/modified tools

Setting Up Integration Tests

Prerequisites

  1. Apple Mail configured with at least one account
  2. macOS Automation permission granted to Terminal/IDE

Test Account Setup

# Set test account (default: "Gmail")
export MAIL_TEST_ACCOUNT="Gmail"

# Run integration tests
make test-integration

Running Tests

# Integration tests are opt-in
pytest tests/integration/ --run-integration -v

# Or via Makefile
make test-integration

Writing Integration Tests

import pytest
from apple_mail_fast_mcp.mail_connector import AppleMailConnector

# Skip unless explicitly enabled
pytestmark = pytest.mark.skipif(
    "not config.getoption('--run-integration')",
    reason="Integration tests disabled by default."
)

class TestMailIntegration:
    @pytest.fixture
    def connector(self) -> AppleMailConnector:
        return AppleMailConnector()

    @pytest.fixture
    def test_account(self) -> str:
        import os
        return os.getenv("MAIL_TEST_ACCOUNT", "Gmail")

    def test_list_mailboxes(self, connector, test_account):
        """Verify we can list mailboxes from a real account."""
        result = connector.list_mailboxes(test_account)
        assert isinstance(result, list)
        assert len(result) > 0
        # INBOX should always exist
        assert any("INBOX" in mb for mb in result)

    @pytest.mark.skip(reason="Sends real email - enable manually")
    def test_draft_send_now(self, connector):
        """Test sending a draft - enable manually only."""
        ...

Read the full file on GitHub · 135 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. 11d ago First seen · 135 lines · 52 tokens per session scan A 28042c671993

Subscribe to this mod's changes

integration-testing is a skill published in the GitHub repository s-morgan-jeffries/apple-mail-fast-mcp (102 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,038 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

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

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

bulk-operation-preview

Show structured preview of bulk email operations (5+ emails) before execute. Group by thread, flag false-positive candidates, count side-effect scope (files written, attachments downloaded, mailboxes touched). Use after email-search-disambiguation finishes Phase 1, as Phase 2 of the confirmation protocol.

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

email-search-disambiguation

A clarification step for email searches when a person, time period, direction, or scope is unclear. It presents specific possible meanings so the user can choose one.

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

email-compose-review

Use this skill any time you are writing an email or reply on behalf of the user via the apple-mail MCP tools (composeemail, replyemail). This means any time the user asks you to "write", "draft", "compose", "send", or "reply to" an email — even if they phrase it casually. Run every LLM-drafted body through a…

jayvee6/apple-mail-mcp · 121 tokens

swift-testing-pro

Writes, reviews, and improves Swift Testing code using modern APIs and best practices. Use when reading, writing, or reviewing projects that use Swift Testing.

jacklandrin/OnlySwitch · 34 tokens