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/nanocoai/nanoclaw/add-imessagenpx skills add nanocoai/nanoclaw --skill add-imessagegit clone --depth 1 https://github.com/nanocoai/nanoclawWhat 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.00092 | $0.03386 |
| Opus 5 | $0.00046 | $0.01693 |
| Sonnet 5 | $0.00018 | $0.00677 |
| Haiku 4.5 | $0.00009 | $0.00339 |
Grade A, and why
add-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 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add iMessage
NanoClaw talks to iMessage through a single imessage channel with two
pluggable backends:
- Local (this Mac) — the Chat SDK bridge over
chat-adapter-imessage, reading this Mac's signed-in iMessage account (chat.db). macOS only; the Node binary needs Full Disk Access. - Hosted iMessage (via photon.codes) — a native adapter over Photon's
spectrum-tsgRPC stream. The hosted service owns the iMessage line, so there's no Mac relay, webhook, or public URL. Works on any OS, and a device-login flow provisions everything for you.
Both register the same imessage channel type; only one runs per install.
NanoClaw doesn't ship channels in trunk — this skill copies the unified
imessage adapter in from the channels branch. Full reference:
docs/imessage.md.
The mechanical steps under Apply carry nc: directive fences: an agent reads
the prose and applies them, and a parser can apply them deterministically from
the same document. Every directive is idempotent, so the whole skill is safe to
re-run; anything a parser can't apply falls back to the prose beside it.
Apply
1. Choose a backend
Pick the backend first — it decides which package gets installed and which walkthrough runs below (the other backend's steps are skipped):
How should iMessage run — `local` (this Mac's signed-in iMessage account; macOS only, needs Full Disk Access) or `hosted` (a managed line via photon.codes; works on any OS)?
The local backend only works on a Mac — it reads this machine's iMessage
chat.db directly, and there is no such database off macOS. On any other OS,
stop here and choose hosted instead; otherwise you'd write a local config
that can never receive a message:
[ "$(uname)" = Darwin ]
2. Copy the adapter
Fetch the channels branch and copy the unified iMessage adapter and its tests
into src/channels/:
src/channels/imessage.ts
src/channels/imessage.test.ts
src/channels/imessage-registration.test.ts
What ships with it
3 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 First seen · 317 lines · 92 tokens per session scan A 5bd6f3577187
add-imessage is a skill published in the GitHub repository nanocoai/nanoclaw (30,661 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 3,386 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-30.
Other skills, from other repositories
render-style
House style for the renderhtml tool — dark dashboard / architecture-diagram look with stat tiles, bar rows, numbered timeline steps, two-panel grids, status pills, connector arrows, callout bands, and verdict blocks. Read this skill before calling renderhtml so the output is visually consistent. Provides CSS tokens…
self-reflection
Daily loop that reviews the bot's own recent outbound behavior and any pending lessons in self/learnings.md, stress-tests candidate rules against 10-20 hypothetical scenarios, and on explicit owner approval routes each to the right home among three sinks — prompts/project.md (durable behavioral rules), a memory file…
reminder-format
House format for the text passed to reminderset. Read before calling reminderset, and again before editing a reminder (cancel + re-create). Three rules — open with the literal marker , state the goal in one line, then list numbered steps the future-self should run when the reminder fires. Keeps fired envelopes…
openclaw-control
控制和管理 OpenClaw AI 助手。用于发送消息给 OpenClaw、检查状态、管理配置和安装技能。当用户想要与 OpenClaw 交互或管理 OpenClaw 时使用此技能。.
Pynchy Development
Use when running pynchy locally — running the app, tests, linting, formatting, prek hooks, or rebuilding the agent container. Also use when determining whether you're on the live Pynchy host or a local machine, and for debugging agent behavior-- session transcript branching, inspecting message history and agent traces…
Pynchy Plugin Authoring
Use when creating, scaffolding, or updating a pynchy plugin, including channels, MCP servers, skills, agent cores, workspace specs, and container runtime plugins. Also use when users ask how to register plugins via config.toml, add entry points, or validate plugin hook wiring.