ai-memory is a shared long-term memory system for coding agents that preserves project knowledge, unfinished work, failed approaches, and open questions across tools and machines. It is used by individual developers and teams to hand work between different coding agents and continue projects without repeating the context.
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 akitaonrails/ai-memory --skill ai-memory-messaginggit clone --depth 1 https://github.com/akitaonrails/ai-memoryWrote 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/akitaonrails/ai-memory/ai-memory-messaging)<a href="https://agentmods.dev/skills/akitaonrails/ai-memory/ai-memory-messaging"><img src="https://agentmods.dev/badge/skills/akitaonrails/ai-memory/ai-memory-messaging/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/akitaonrails/ai-memory/ai-memory-messaging"><img src="https://agentmods.dev/badge/skills/akitaonrails/ai-memory/ai-memory-messaging.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.00063 | $0.01112 |
| Opus 5.5 | $0.00025 | $0.00445 |
| Sonnet 5.5 | $0.00013 | $0.00222 |
| Haiku 4.5 | $0.00006 | $0.00111 |
Grade A, and why
ai-memory-messaging 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 16d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-memory cross-project messaging
Use this skill when work needs to move between two DIFFERENT projects without pulling one project's context into the other's session. It is a directed, claim-once inbox/queue: an agent in project A drops a self-contained request into project B's inbox; a session in B pops it exactly once and acts on it. This is distinct from handoffs, which are same-project session continuity.
Tools in this cluster
memory_message_sendsends a message to another project's inbox. Requiresto_workspace+to_project(the recipient must already exist — an unknown target is rejected, never created). Put a SELF-CONTAINED request inbody: the recipient works from it alone, without your project's context. Use it when the user wants an agent in another repo to do something and you should not learn that repo here. The sender (from_workspace+from_project) is the provenance the recipient judges your request by: static clients must name it, and a send whose sender the server would have to guess is refused.memory_message_listis the read-only inspect path.box="inbox"(default) shows mail addressed to this project (what you can pop);box="outbox"shows mail this project has sent (what you can cancel). Nothing is consumed. When the call named no project and was not bound to your hook session, the response addsresolved_scope,scope_source, andhint: check thatresolved_scopeis the mailbox you meant before acting on the list.memory_message_popclaims ONE message exactly once — the oldest, or a specificmessage_id. Use it when the user asks to check the inbox or the session-start notice reports waiting mail; pass theworkspaceandprojectthat notice (or the project briefing'sscopefield) names. A pop whose inbox the server would have to guess is refused and claims nothing. A later pop returns null once the inbox is empty.memory_message_cancelretracts pending mail you SENT: a specificmessage_id, or every pending message this project sent when omitted. Use it when the user gives up on a request. It only affects your own outbound mail, and like pop it refuses a guessed project.
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.
- 16d ago Changed · +2 lines 3b76b008086a
- 20d ago Changed f72b829a035b
- 1mo ago First seen · 34 lines · 63 tokens per session scan A 7a86bdd78e94
ai-memory-messaging is a skill published in the GitHub repository akitaonrails/ai-memory (13,818 stars, last pushed today), licensed MIT. It adds 63 tokens to every session and 1,112 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-09-17.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…