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/njerschow/textme/imessagenpx skills add njerschow/textme --skill imessagegit clone --depth 1 https://github.com/njerschow/textmeWrote 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/njerschow/textme/imessage)<a href="https://agentmods.dev/skills/njerschow/textme/imessage"><img src="https://agentmods.dev/badge/skills/njerschow/textme/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.00000 | $0.00980 |
| Opus 5 | $0.00000 | $0.00490 |
| Sonnet 5 | $0.00000 | $0.00196 |
| Haiku 4.5 | $0.00000 | $0.00098 |
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 6d 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iMessage Skill
Description
Send and receive iMessages via Claude Code. Get real-time input from the user via their phone, similar to how call-me enables voice conversations.
When to Use This Skill
Use ask_user when:
- You've completed significant work and want to report status and ask what's next
- You need real-time input for decisions
- You're blocked and need clarification to proceed
- You want to discuss next steps with the user
Use notify_user when:
- You want to send a status update without needing a response
- The information is non-urgent
- You don't want to block waiting for a reply
Do NOT use for:
- Simple yes/no questions that can be asked in the terminal
- Information the user has already provided
- Sending to non-whitelisted numbers
Primary Tools
ask_user
Send an iMessage and wait for the user to respond. This is the main tool - similar to initiate_call in call-me.
Parameters:
message(string, required): What to ask the user. Be conversational.timeout_seconds(number, optional): How long to wait (default: 300 = 5 minutes)
Behavior:
- Sends iMessage to the user
- Waits for response (polls every 5 seconds)
- Returns the user's response when received
- If timeout: returns notice, response will be picked up later via
check_messages
Example:
ask_user({ message: "Finished the auth module. Should I work on API endpoints or tests next?" })
→ User responds via phone: "API endpoints"
→ Returns: "User responded: API endpoints"
→ Claude continues working on API endpoints
notify_user
Send an iMessage without waiting for a response. Fire-and-forget.
Parameters:
message(string, required): Message to send
Example:
notify_user({ message: "Starting the database migration. This will take about 10 minutes." })
→ Returns immediately: "Notification sent"
→ Claude continues working
Secondary Tools
check_messages
Check for pending iMessages. Use this to pick up responses that arrived after a timeout.
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.
- 6d ago First seen · 126 lines · 0 tokens per session scan A fb40b23552ea
imessage is a skill published in the GitHub repository njerschow/textme (93 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 980 tokens. 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
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.