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 nataliacorrea03/claude-code-skills --skill imessagegit clone --depth 1 https://github.com/nataliacorrea03/claude-code-skillsWrote 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/nataliacorrea03/claude-code-skills/imessage)<a href="https://agentmods.dev/skills/nataliacorrea03/claude-code-skills/imessage"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/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/skills/nataliacorrea03/claude-code-skills/imessage"><img src="https://agentmods.dev/badge/skills/nataliacorrea03/claude-code-skills/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.00143 | $0.01389 |
| Opus 5 | $0.00072 | $0.00694 |
| Sonnet 5 | $0.00029 | $0.00278 |
| Haiku 4.5 | $0.00014 | $0.00139 |
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 9d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
imessage
Read and send iMessages locally. No MCP server, no cloud API. Two modes with very different permission costs.
Requires a Mac with iMessage set up: Messages must be signed into your Apple ID and able to send from this Mac. macOS only, this does not work on Windows, Linux, or from a phone alone.
When to use
- "Text Alex that I'm running 10 min late"
- "Draft an iMessage to [person] saying..."
- "Send Sam a quick text about..."
- "What did [person] text me yesterday?"
- "Pull up my last thread with [person]"
Do NOT use for:
- Slack or other chat apps (use their own tools)
- Email (use an email tool)
- SMS to non-Apple recipients without confirming the contact has iMessage (AppleScript can still route as SMS via the iPhone bridge, but only if Continuity is on)
Modes
Send mode (default, low-permission)
- Confirm recipient and message. Match the tone to the recipient (casual with friends, more measured with colleagues).
- Show the draft. Wait for "send it" or equivalent.
- On approval, send via AppleScript:
osascript <<'APPLESCRIPT'
tell application "Messages"
set targetService to 1st service whose service type = iMessage
set targetBuddy to buddy "PHONE_OR_APPLE_ID" of targetService
send "MESSAGE_TEXT" to targetBuddy
end tell
APPLESCRIPT
Replace PHONE_OR_APPLE_ID with the recipient's phone (E.164, e.g. +19175551234) or Apple ID email. Replace MESSAGE_TEXT with the drafted body, escaping quotes and backslashes for AppleScript.
Permission required: System Settings, Privacy & Security, Automation, enable Messages under Terminal (or iTerm, or whatever shell host Claude Code runs in).
Permission NOT required: Full Disk Access. Send mode does not read chat.db.
Read mode (opt-in, high-permission)
Required for: pulling thread history, searching past messages, triaging recent texts.
Cost: Reading ~/Library/Messages/chat.db requires Full Disk Access for Terminal. FDA is a broad, system-level permission. Once granted, the terminal binary can read all protected user data (Photos, Health, banking caches, and more), not just iMessages. This is the OS design, not a skill choice.
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.
- 9d ago First seen · 106 lines · 143 tokens per session scan A 0e32d3721f73
imessage is a skill published in the GitHub repository nataliacorrea03/claude-code-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 143 tokens to every session and 1,389 once invoked, about $0.0007 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
agent-carnet
Use this skill when the user asks to save, recall, find, or organize notes. Triggers on: 'remember this', 'save this', 'note this', 'what did we discuss about...', 'check the notebook', 'find in carnet'. Also use proactively when discovering findings worth preserving across sessions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
security-audit
Audit a codebase or directory for security issues (hardcoded secrets, injection, unsafe deserialization, weak crypto, authz gaps) and produce a structured findings report. Use when the user asks for a security review, an audit, or to check code for vulnerabilities. Report only — never fix.
taiyi-ui-design
A design-planning guide for describing how an application's user interface should look and behave. It produces a UI-DESIGN.md document covering layouts, components, interactions, accessibility, and error states.
taiyi-evolve
A workflow skill that compares the implemented code with the frozen design after development and testing. It records architecture changes and proposes updates to DESIGN.md, the document describing the intended system structure.
taiyi-diagram-c4
A code-scanning tool that builds C4 architecture documents from a repository. It separates facts observed in the code from conclusions inferred about the design and uses Mermaid diagrams as the source format.