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-retrievalgit 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-retrieval)<a href="https://agentmods.dev/skills/akitaonrails/ai-memory/ai-memory-retrieval"><img src="https://agentmods.dev/badge/skills/akitaonrails/ai-memory/ai-memory-retrieval/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-retrieval"><img src="https://agentmods.dev/badge/skills/akitaonrails/ai-memory/ai-memory-retrieval.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.00065 | $0.01501 |
| Opus 5 | $0.00032 | $0.00750 |
| Sonnet 5 | $0.00013 | $0.00300 |
| Haiku 4.5 | $0.00006 | $0.00150 |
Grade A, and why
ai-memory-retrieval 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 4d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ai-memory retrieval
Use this skill for read-only ai-memory lookups, catch-up, and evaluating remembered project knowledge before you design, debug, or edit.
Tools in this cluster
memory_querysearches the current project's wiki for prior decisions, gotchas, procedures, rules, and session notes.memory_recentlists the most recently updated pages when the user wants a light activity check.memory_read_pagefetches a full page body after a search hit or direct path lookup.memory_read_session_observationsreads one session's raw hook observations (prompts, tool calls, stops) in capture order, paged and body-capped, when the user asks what actually happened in a session or wants to check a compiled page against its evidence.memory_statusreports whether ai-memory is healthy and how large the knowledge base is.memory_briefingreturns a structured read-only snapshot for agent consumption.memory_explorereturns a prose digest when the user asks for an open-ended catch-up.
Project scope
Choose scope from the MCP client's identity support:
- Session-aware MCP clients that forward the real lifecycle-hook session id on every request should use automatic current-project routing. Omit
workspace,project, andcwdfor the current repository; pass explicit scope only when the user names a different project. - Static MCP clients (including clients with lifecycle hooks but no bridge connecting that hook session id to MCP requests) must pass
workspaceandprojecttogether on every project-scoped call, including requests about this project, here, or our work. Read the exact names from the nearest.ai-memory.tomlwhen it declares both. If it does not, obtain the names from the operator or server configuration; never guess them from a directory name and never rely on the server's last active project.
This rule applies only to project-scoped calls. For cross-project retrieval, global=true must omit workspace, project, and scopes. For a standing preference written with scope: "global", omit workspace and 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.
- 4d ago Changed · +5 lines 838eed977750
- 12d ago First seen · 85 lines · 65 tokens per session scan A 31de3bbcc3ff
ai-memory-retrieval is a skill published in the GitHub repository akitaonrails/ai-memory (6,432 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 1,501 once invoked, about $0.0003 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
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.