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 byte5ai/palaia --skill palaia-messengergit clone --depth 1 https://github.com/byte5ai/palaiaWrote 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/byte5ai/palaia/palaia-messenger)<a href="https://agentmods.dev/skills/byte5ai/palaia/palaia-messenger"><img src="https://agentmods.dev/badge/skills/byte5ai/palaia/palaia-messenger/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/byte5ai/palaia/palaia-messenger"><img src="https://agentmods.dev/badge/skills/byte5ai/palaia/palaia-messenger.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00082 | $0.02008 |
| Opus 5.5 | $0.00033 | $0.00803 |
| Sonnet 5.5 | $0.00016 | $0.00402 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
palaia-messenger 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 1mo 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working alongside other sessions
This person often has more than one AI session going at once — another window, another machine, a different tool entirely — sometimes on the same piece of work. The directory is how sessions find each other; the messenger is how they talk once found. Both are ordinary parts of doing the work, not something to ask permission for.
Do this without being asked
Three moments, every time:
- Starting a task. Register with the directory, describing what you are about to do in your own words. Anyone else working nearby can now find you.
- Picking up a task, especially one that sounds like a continuation. Check for anything waiting for you before you start — a handoff, a question, a heads-up. Acting on stale information because you never looked is the failure this exists to prevent.
- A message asks you for a reply. Answer it, or say plainly that you will not — in the same turn you notice it, not later. A message marked as needing an answer that never gets one leaves the sender waiting on nothing.
None of this is a favour to the person watching. It is the same habit as checking a shared document before editing it.
The tools
| Tool | Use it for |
|---|---|
directory_register |
Announce this session: what you're doing, at the start of a task. |
directory_heartbeat |
Keep your registration alive during a long task. |
directory_update |
Change what you're doing, or mark yourself idle. |
directory_list / directory_query |
Find another live session — by what it's doing, or by a tag it offers. |
directory_deregister |
Leave the directory when a task wraps up. |
messenger_send |
Send one message to a session, or to several at once. |
messenger_check |
Collect whatever has arrived for you. |
messenger_ack |
Close a message once you've dealt with it. |
messenger_thread |
Read a whole back-and-forth, not just the latest message. |
These names are fixed — they do not carry a per-person prefix the way the memory tools do. Use the ones your client actually lists.
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.
- 1mo ago Changed · -6 lines 41f9f66554a4
- 2mo ago First seen · 188 lines · 82 tokens per session scan A 5fc054a9bcf9
palaia-messenger is a skill published in the GitHub repository byte5ai/palaia (20 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 2,008 once invoked, about $0.0003 per session on Opus 5.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.
palaia-messenger compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| palaia-messengerbyte5ai/palaia | Skill | 20 | 4d ago | MIT | A | 82 | Claude Code |
| setupAbsoluteMode/session-recall | Skill | 13 | 13d ago | MIT | A | 84 | Claude Code |
| session-recallAbsoluteMode/session-recall | Skill | 13 | 13d ago | MIT | A | 92 | Claude Code |
| memxNeoLi00/memX | Skill | 400 | 5mo ago | MIT | A | 26 | Claude Code |
| mission-controlbuilderz-labs/mission-control | Skill | 6.5k | 6d ago | MIT | A | 34 | Claude Code, Codex |
| memory-to-skillzilliztech/memsearch | Skill | 2.8k | 2d ago | MIT | A | 82 | Claude Code, Codex |
| remember-sessiondoobidoo/mcp-memory-service | Skill | 2.1k | today | Apache-2.0 | A | 68 | Claude Code |