apple-mail-mcp: Skill for Claude Code

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

integration-testing is a skill for Claude Code, Codex from LeChabrax/apple-mail-mcp. It costs 52 tokens per session (1,037 once invoked), scanned A, a copy of integration-testing, MIT.

A guide to testing Apple Mail integrations against the real Mail app. Integration tests check how separate parts work together, rather than testing one piece in isolation.

In plain words
What is it for?
Setting up and debugging tests for new AppleScript operations, modified tools, and full MCP connections.
Why use it?
Mocked unit tests can miss AppleScript errors, Mail.app behavior, account differences, and timeout problems.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

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

Reuse

Borrowing it

Nothing to install: this file belongs to LeChabrax/apple-mail-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/LeChabrax/apple-mail-mcp/main/.grok/skills/integration-testing/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/LeChabrax/apple-mail-mcp

Made for: Claude Code, Codex.

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/lechabrax/apple-mail-mcp/integration-testing/github.svg)](https://agentmods.dev/skills/lechabrax/apple-mail-mcp/integration-testing)
Your own site
<a href="https://agentmods.dev/skills/lechabrax/apple-mail-mcp/integration-testing"><img src="https://agentmods.dev/badge/skills/lechabrax/apple-mail-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/lechabrax/apple-mail-mcp/integration-testing"><img src="https://agentmods.dev/badge/skills/lechabrax/apple-mail-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,037 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.
Origin 100% copy Near-identical to another mod 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.01037
Opus 5.5 $0.00021 $0.00415
Sonnet 5.5 $0.00010 $0.00207
Haiku 4.5 $0.00005 $0.00104

Measured 1mo ago against content hash cb639b43a609, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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

This is a copy

100% identical to integration-testing — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.grok/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_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. 1mo ago First seen · 135 lines · 52 tokens per session scan A cb639b43a609

Subscribe to this mod's changes

integration-testing is a skill published in the GitHub repository LeChabrax/apple-mail-mcp (0 stars, last pushed 17d ago), licensed MIT. It adds 52 tokens to every session and 1,037 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to integration-testing, differing in 2 lines, and is treated as a copy.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens