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 skills add linq-team/claude-code-imessage-channel --skill imessagegit clone --depth 1 https://github.com/linq-team/claude-code-imessage-channelWrote 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/linq-team/claude-code-imessage-channel/imessage)<a href="https://agentmods.dev/skills/linq-team/claude-code-imessage-channel/imessage"><img src="https://agentmods.dev/badge/skills/linq-team/claude-code-imessage-channel/imessage.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.1 | $0.00031 | $0.00542 |
| Opus 5 | $0.00015 | $0.00271 |
| Sonnet 5 | $0.00006 | $0.00108 |
| Haiku 4.5 | $0.00003 | $0.00054 |
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 7d 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
You have access to iMessage via the Linq API. You can:
- Reply to inbound messages using the
replytool with thechat_idfrom the channel event - Send new messages to any phone number using the
sendtool - React to messages with tapbacks (like, love, laugh, dislike, emphasize, question) using the
reacttool - Edit a previously sent message using
edit_messagefor streaming progress updates - Effects — add iMessage effects to reply or send with the optional
effectparameter:- Screen:
confetti,fireworks,lasers,sparkles,celebration,hearts,love,balloons,happy_birthday,echo,spotlight - Bubble:
slam,loud,gentle,invisible
- Screen:
- Threading — reply to a specific message by passing
reply_to(message ID) in thereplytool. The message_id is available in the channel event metadata. - Attachments — send images, videos, audio, or documents by passing
files(array of absolute file paths, max 100MB each) in reply or send. Files are uploaded automatically via the Linq API. Inbound attachments show as download URLs in the channel event. - Text decorations — style text with
text_decorationson reply or send. Each decoration hasrange: [start, end)and eitherstyle(bold, italic, strikethrough, underline) oranimation(big, small, shake, nod, explode, ripple, bloom, jitter). iMessage only. - Rich links — send a URL with a preview card using
send_linkwithchat_idandurl. The link must be the only content in the message. - Capability check — use
check_capabilityto check if a phone number supports iMessage or RCS before sending.
When channel events arrive as <channel source="imessage">, respond naturally and concisely - this is iMessage, keep it brief.
Read receipts and typing indicators are handled automatically.
Configuration
Credentials are stored in ~/.claude/channels/imessage/.env. Run /imessage:configure to manage them.
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.
- 7d ago First seen · 28 lines · 31 tokens per session scan A 543627d72646
imessage is a skill published in the GitHub repository linq-team/claude-code-imessage-channel (24 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 542 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.
Other skills, from other repositories
c-messaging
Send and read messages via imsg (iMessage) and wacli (WhatsApp). Supports sending to individuals or groups, reading recent conversations, and checking unread messages across both platforms.
imessage
Skill "imessage" from furkangonel/cowrangler, covering imessage, ön koşullar, ne zaman kullan, ne zaman kullanma and hızlı referans.
willitsend
Preflight outbound SMS/iMessage for silent carrier filtering, segment blowups, and dropped iMessage features before sending.
imsg-rpc
Set up, maintain, and debug the imsg-rpc Unix socket daemon that gives the gateway iMessage access via JSON-RPC. Covers FDA setup, code signing, launchd service, and the imsg source repo.
imsg
Read and send iMessages and SMS from the terminal via the imsg CLI.
forge-cli
A command-line management tool for Forge Hub, a service that connects agent instances to chat channels and routes messages between them.