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/trtmn/agent-plugins/imsgnpx skills add trtmn/agent-plugins --skill imsggit clone --depth 1 https://github.com/trtmn/agent-pluginsWhat 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.00118 | $0.02355 |
| Opus 5 | $0.00059 | $0.01177 |
| Sonnet 5 | $0.00024 | $0.00471 |
| Haiku 4.5 | $0.00012 | $0.00235 |
Grade A, and why
imsg 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 — 254 lines — stays where its author put it; the contents beside it link to each section on GitHub.
imsg
The imsg command-line tool enables you to send and read iMessage and SMS messages directly from the terminal, query your Messages database, and watch for incoming messages.
⚠️ Important Privacy & Database Notes
- Database Access:
imsgreads from your local Messages database (~/Library/Messages/chat.db). This is a sensitive file containing your complete message history. - Permissions: macOS may prompt for permissions when accessing the Messages database. Terminal needs Full Disk Access on newer macOS versions.
- Data Sensitivity: Be cautious when working with message history — it contains private conversations.
- Database Locking: If Messages.app is open, the database may be locked. Close Messages.app if you encounter access issues.
Commands Overview
imsg has four main commands:
chats— List your recent iMessage/SMS conversationshistory— Show message history for a specific chatwatch— Stream incoming messages in real-timesend— Send a message (text and/or attachment)rpc— Run JSON-RPC over stdin/stdout (advanced)
chats — List Conversations
List recent iMessage and SMS conversations from your Messages database.
Usage
imsg chats [options]
Options
--limit <number>— Number of chats to list (e.g.,--limit 5)--jsonor-j— Output as machine-readable JSON--db <path>— Custom path to chat.db (defaults to~/Library/Messages/chat.db)-v, --verbose— Enable verbose logging--log-level <level>— Set log level:trace|verbose|debug|info|warning|error|critical
Examples
# List 10 most recent conversations
imsg chats --limit 10
# List conversations as JSON (easier to parse)
imsg chats --limit 5 --json
# List all conversations (no limit)
imsg chats
history — Show Message History
Retrieve message history for a specific conversation. Requires a chat ID (which you get from imsg chats).
Usage
imsg history [options]
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 First seen · 254 lines · 118 tokens per session scan A 92c9cb0f2678
imsg is a skill published in the GitHub repository trtmn/agent-plugins (2 stars, last pushed 5d ago), licensed Unlicense. It adds 118 tokens to every session and 2,355 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.