Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/isityael/apple-mail-mcp/applescript-patternsnpx skills add isityael/apple-mail-mcp --skill applescript-patternsgit clone --depth 1 https://github.com/isityael/apple-mail-mcpWrote 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/isityael/apple-mail-mcp/applescript-patterns)<a href="https://agentmods.dev/skills/isityael/apple-mail-mcp/applescript-patterns"><img src="https://agentmods.dev/badge/skills/isityael/apple-mail-mcp/applescript-patterns.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00056 | $0.00983 |
| Opus 5 | $0.00028 | $0.00491 |
| Sonnet 5 | $0.00011 | $0.00197 |
| Haiku 4.5 | $0.00006 | $0.00098 |
Grade A, and why
applescript-patterns 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 2d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AppleScript Generation Patterns
Follow these patterns when writing or modifying AppleScript templates in apple_mail_mcp/tools/*.py.
Escaping User Input
NEVER interpolate user strings directly into AppleScript f-strings. Always use escape_applescript() from core.py:
from apple_mail_mcp.core import escape_applescript
safe_account = escape_applescript(account)
safe_keyword = escape_applescript(subject_keyword)
script = f'''
tell application "Mail"
set targetAccount to account "{safe_account}"
...
end tell
'''
escape_applescript() handles: backslashes, double quotes, carriage returns, newlines, and tabs. This prevents AppleScript injection via user-controlled strings.
Mailbox Handling
Use get_mailbox_script() for any mailbox access. It handles the INBOX/Inbox inconsistency in macOS Mail:
from apple_mail_mcp.core import get_mailbox_script
# Generates try/catch with INBOX->Inbox fallback
mailbox_setup = get_mailbox_script(mailbox, "targetMailbox", "targetAccount")
script = f'''
tell application "Mail"
set targetAccount to account "{safe_account}"
{mailbox_setup}
...
end tell
'''
For inbox specifically, use inbox_mailbox_script():
from apple_mail_mcp.core import inbox_mailbox_script
script = f'''
{inbox_mailbox_script("inboxMailbox", "targetAccount")}
'''
Recipients (TO/CC/BCC)
Use recipients_script() for adding recipients to outgoing messages:
from apple_mail_mcp.core import recipients_script
to_script = recipients_script(to, "to", "newMessage")
cc_script = recipients_script(cc, "cc", "newMessage")
bcc_script = recipients_script(bcc, "bcc", "newMessage")
This handles comma-separated addresses, escaping each one, and generating the correct make new ... recipient AppleScript.
Iteration Direction
When mutating a collection (moving or deleting messages), ALWAYS iterate in reverse to avoid index shifting:
-- CORRECT: reverse iteration during mutation
set msgCount to count of inboxMessages
repeat with i from msgCount to 1 by -1
set aMessage to item i of inboxMessages
move aMessage to targetMailbox
end repeat
-- WRONG: forward iteration skips items after mutation
repeat with aMessage in inboxMessages
move aMessage to targetMailbox -- shifts subsequent indices
end repeat
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.
- 2d ago First seen · 157 lines · 56 tokens per session scan A 63324f523ce7
applescript-patterns is a skill published in the GitHub repository isityael/apple-mail-mcp (0 stars, last pushed 7d ago), licensed MIT. It adds 56 tokens to every session and 983 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…