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/cyberpapiii/imessage-max/using-imessage-maxnpx skills add cyberpapiii/imessage-max --skill using-imessage-maxgit clone --depth 1 https://github.com/cyberpapiii/imessage-maxWrote 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/cyberpapiii/imessage-max/using-imessage-max)<a href="https://agentmods.dev/skills/cyberpapiii/imessage-max/using-imessage-max"><img src="https://agentmods.dev/badge/skills/cyberpapiii/imessage-max/using-imessage-max.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.00083 | $0.01442 |
| Opus 5 | $0.00042 | $0.00721 |
| Sonnet 5 | $0.00017 | $0.00288 |
| Haiku 4.5 | $0.00008 | $0.00144 |
Grade A, and why
using-imessage-max 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 yesterday.
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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using iMessage Max
Overview
Use this skill to choose the right iMessage Max tool sequence for the user's intent.
Start broad when completeness matters, then narrow. Unread-only and activity-only views miss things. Do not let either stand in for a full recent overview unless the user asked for that narrower slice.
When reporting results back to the user, use human chat names and participant names. Treat chat_id values such as chat123 as internal handles for follow-up tool calls and exact sends; do not refer to conversations as "Chat 123" in user-facing prose when chat.name, name, or participant labels are available.
Workflow guide
Broad catch-up or daily sweep
Use this when the user says things like:
- "catch me up on everything I missed"
- "morning sweep"
- "what happened in the last day or two"
- "show me what I should know from my texts"
Default flow:
- Start with
list_chatsusing a recent window such assince="1d"orsince="2d"andsort="recent". - Use
get_unreadas a cross-check for still-unread threads and message-level unread review when needed. - Use
get_active_conversationsonly to prioritize which recent threads may deserve attention first. - Use
get_messagesto drill into the chats surfaced by the overview. If you already hold anext_rowidfrom a previous turn, callget_messages_sincewith it instead ofget_unread.
Why:
list_chatsgives the safest broad preview across recent conversations.get_unreadis narrower and can miss important chats that were already opened.get_active_conversationsis also narrower and can miss quiet but important threads.list_chats,search,get_unread, andfind_chathide junk and unknown-sender chats by default and report how many infiltered_hidden. Only passinclude_filtered=truewhen the user asks about a message that did not show up.
Targeted lookup
Use this when the user already knows the person, thread, or topic.
- If they know the person or chat identity, start with
find_chat. - If they already know the exact thread, use
get_chat_detailsbefore opening message history. - If they know the topic but not the chat, start with
search. - Then use
get_messagesorget_contextto read the relevant section in detail.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday Changed · +5 lines 5afb3f350eb7
- 5d ago First seen · 115 lines · 83 tokens per session scan A 15ca9bb71a55
using-imessage-max is a skill published in the GitHub repository cyberpapiii/imessage-max (6 stars, last pushed yesterday), licensed MIT. It adds 83 tokens to every session and 1,442 once invoked, about $0.0004 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
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.