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 bowlofarugula/texting --skill texting-listengit clone --depth 1 https://github.com/bowlofarugula/textingWrote 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/bowlofarugula/texting/texting-listen)<a href="https://agentmods.dev/skills/bowlofarugula/texting/texting-listen"><img src="https://agentmods.dev/badge/skills/bowlofarugula/texting/texting-listen.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.00092 | $0.00893 |
| Opus 5 | $0.00046 | $0.00447 |
| Sonnet 5 | $0.00018 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
texting-listen 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.
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/texting-listen — watch a thread for new messages
Arguments passed: $ARGUMENTS (e.g. "alex", "sam until she confirms")
This is a session-bound listener: it works only while this session is open and the Mac is awake. Say so up front in one line when starting. For true 24/7 unattended response, this is the wrong tool — see docs/AUTOREPLY.md and its tradeoffs.
Start
- Resolve the contact from
list_chatsoutput — rows carry contact and display names next to the handle/chat_id(no manual Contacts lookup; the engine labels chats itself). Ambiguous or missing → ask. - Establish a baseline:
read_messagesfor that chat (pass the handle aschat); note the ISO timestamp and content of the latest message. Report the baseline to the user. - Ask (or infer from the request) what to do on arrival: just notify, or notify + draft a reply for approval.
Poll loop
For long-running, across-turn monitoring this skill polls with ScheduleWakeup
(below) — that's the primary loop, because it doesn't hold a turn open. The
watch MCP tool is the other option: it blocks up to ~60s waiting for the
next message and is the right pick only for a short, active wait inside one
turn ("hold on for her reply"), not for monitoring that should span minutes or
hours. Pass the cursor it returns back as since_rowid to avoid missing
anything between waits.
Schedule a wakeup (ScheduleWakeup) carrying a self-contained prompt: contact name, handle, baseline timestamp, and the on-arrival behavior. Cadence:
- Actively waiting on a specific reply ("tell me when she confirms") → ~270s, staying inside the prompt-cache window.
- Casual monitoring ("keep an eye on the thread") → 1200–1800s; don't burn a cache miss every 5 minutes for a thread that moves hourly.
On each wakeup: read_messages with since set to the baseline timestamp
(returns only messages at/after it), diff against the baseline, and:
- Nothing new → reschedule silently. Do not re-summarize the thread.
- New inbound message → surface it (sender, time, text). Send a PushNotification if the user is likely away — a new message from the watched contact is exactly the "they'd act on it now" case. Then follow the agreed on-arrival behavior. Update the baseline and reschedule (unless the goal is met, e.g. "until she confirms" — then stop and say the watch is done).
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 · 75 lines · 92 tokens per session scan A 0e66a88510b8
texting-listen is a skill published in the GitHub repository bowlofarugula/texting (1 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 92 tokens to every session and 893 once invoked, about $0.0005 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
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.
imsg
Read and send iMessages and SMS from the terminal via the imsg CLI.
imessage-send
Send a message by name or number.
imessage-group-create
Create a new group chat with contacts.
imessage-read
Read messages by contact or group.