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.
git clone --depth 1 https://github.com/esaruoho/appleWrote 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/commands/esaruoho/apple/imessage)<a href="https://agentmods.dev/commands/esaruoho/apple/imessage"><img src="https://agentmods.dev/badge/commands/esaruoho/apple/imessage/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.
<a href="https://agentmods.dev/commands/esaruoho/apple/imessage"><img src="https://agentmods.dev/badge/commands/esaruoho/apple/imessage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00088 | $0.00561 |
| Opus 5.5 | $0.00035 | $0.00224 |
| Sonnet 5.5 | $0.00018 | $0.00112 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
imessage 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 2mo 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.
What it actually says
/imessage
Send an iMessage to yourself (or anyone) from the terminal — text or files.
/imessage "yo yo yo hi hi hi"
/imessage file.pdf
/imessage --text "see attached" file.pdf
/imessage --to +358401234567 "hello"
/imessage --to [email protected] ~/Downloads/foo.shortcut
Detection
- If the positional argument is an existing file path → attach as file.
- Otherwise → send as text.
- Use
--textor--fileto force a mode explicitly.
Why files need a different path than text
tell application "Messages" to send (POSIX file "...") to buddy ... reliably no-ops on macOS Sequoia (the call succeeds but no attachment renders). The only working path is:
- Set the macOS clipboard to a file reference via Finder
open imessage://<buddy>to focus that thread- UI-script Cmd-V then Return via System Events
The CLI does all three transparently.
First-run setup
The first imessage <file> invocation triggers an Accessibility TCC prompt for the terminal app (Terminal, iTerm, or whatever your shell runs in). Accept it once — System Settings → Privacy & Security → Accessibility → add the terminal app. Subsequent calls are silent.
Default buddy
[email protected]. Override per-call with --to, or set IMESSAGE_TO in your shell profile.
Troubleshooting
- "UI-script paste failed: AppleEvent timed out" — System Events is wedged.
killall "System Events"to restart its daemon, retry. - File "sent" but no attachment — Messages's own Apple-Event handler was busy. Wait a few seconds and retry; the script has a
with timeoutguard so it won't hang forever. - Text-only sends fine, files fail — Accessibility permission missing for the terminal app.
Source: bin/imessage. See also: wiki/concepts/imessage-from-terminal.md.
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.
- 2mo ago First seen · 50 lines · 88 tokens per session scan A d68f7b4e0ca0
imessage is a command published in the GitHub repository esaruoho/apple (15 stars, last pushed 2d ago), licensed MIT. It adds 88 tokens to every session and 561 once invoked, about $0.0004 per session on Opus 5.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.
imessage compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| imessageesaruoho/apple | Command | 15 | 2d ago | MIT | A | 88 | Claude Code |
| wsdanielmiessler/LifeOS | Command | 20k | yesterday | MIT | A | 0 | Claude Code |
| cancel-ralphanthropics/claude-plugins-official | Command | 46k | yesterday | Apache-2.0 | A | 4 | Claude Code |
| engage.actionshypnguyen1209/offensive-claude | Command | 412 | 15d ago | MIT | A | 11 | Claude Code |
| focusData-Wise/claude-plugins | Command | 7 | yesterday | MIT | A | 0 | Claude Code |
| stuckData-Wise/claude-plugins | Command | 7 | yesterday | MIT | A | 0 | Claude Code |
| quickstartorq-ai/assistant-plugins | Command | 6 | 2d ago | MIT | A | 23 | Claude Code |