palaia-memory

palaia-memory is a skill for Claude Code from byte5ai/palaia. It costs 127 tokens per session (2,893 once invoked), scanned A, original, MIT.

A shared memory system stored as plain files on the person's machine. It keeps project decisions, conventions, people, important details, and information about the AI tools they use.

In plain words
What is it for?
Use it to check stored context before answering questions about the person's work and save decisions, conventions, corrections, or other details worth remembering.
Why use it?
It lets assistants recall relevant context across conversations and tools, reducing repeated explanations and forgotten decisions.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the palaia-memory plugin — 4 skills shipped together

Good fit Use it to check stored context before answering questions about the person's work and save decisions, conventions, corrections, or other details worth remembering.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/byte5ai/palaia/palaia-memory
Install

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.

Any agent
npx skills add byte5ai/palaia --skill palaia-memory
Clone the repo
git clone --depth 1 https://github.com/byte5ai/palaia

Made for: Claude Code.

Or install palaia-memory, the plugin that ships this one along with the rest of its 4 skills.

Wrote 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.

agentmods badge for palaia-memory

README.md
[![agentmods](https://agentmods.dev/badge/skills/byte5ai/palaia/palaia-memory/github.svg)](https://agentmods.dev/skills/byte5ai/palaia/palaia-memory)
Your own site
<a href="https://agentmods.dev/skills/byte5ai/palaia/palaia-memory"><img src="https://agentmods.dev/badge/skills/byte5ai/palaia/palaia-memory/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.

agentmods 80×15 button for palaia-memory

Your own site · 80×15
<a href="https://agentmods.dev/skills/byte5ai/palaia/palaia-memory"><img src="https://agentmods.dev/badge/skills/byte5ai/palaia/palaia-memory.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 127 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,893 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00127 $0.02893
Opus 5.5 $0.00051 $0.01157
Sonnet 5.5 $0.00025 $0.00579
Haiku 4.5 $0.00013 $0.00289

Measured 22d ago against content hash d93b22776e83, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

palaia-memory 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 22d 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.

v3/clients/skills/palaia-memory/SKILL.md · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Shared memory

This person keeps one memory that every assistant they use can read and write. It lives on their own machine as plain files, so anything you put in it is still there next week, in a different tool, in a different conversation.

Do this before you answer

Two checks, in this order, every turn — before you write your reply, not after:

  1. Did they just tell me something worth keeping? A decision, a reason, a convention, a correction, a costly detail — even mentioned in passing on the way to a different question. If yes, capture it now. Answering first ends the turn and loses it.
  2. Do I need to look something up? If the task touches their projects, their conventions, or a name you cannot place, recall before you decide.

Then answer, and mention in one short line what you saved.

Neither check is a favour to ask permission for. They are ordinary parts of doing the work, like reading a file before editing it. "Want me to save that?" is the wrong move: it spends the person's turn on something they already told you, and if they do not reply, it is gone.

The tools

The memory arrives as a family of tools whose names carry the memory they belong to — work_memory_recall, personal_memory_capture, and so on. Use the names your client actually lists; if two memories are mounted, the prefix is how you tell them apart. Every tool description says what that memory is for.

Never decide that the memory is unavailable because a start-up notice looked odd or a tool name was not where you expected it. Call memory_status: one cheap call that lists each memory you are connected to, whether you may read and write it, the prefix its tools carry, and how search works. If it answers, the memory is reachable. Only a call that actually fails means it is not.

The ones that matter here:

Tool Use it for
recall What do we know about this topic? Ranked, most useful first.
build_context Pick up where a previous session left off.
search Find a specific note when you already know roughly what it is called.
read Read one note in full.
capture Save something you learned, and move on.
write / edit Only when the person asked you to write or change a note.

Read the full file on GitHub · 235 lines

Changes

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.

  1. 22d ago Changed · +6 lines d93b22776e83
  2. 24d ago Changed · +2 lines f738d7f9eb9b
  3. 1mo ago Changed · +16 lines c1606bfdd7f8
  4. 1mo ago First seen · 211 lines · 127 tokens per session scan A 96992b449a7f

Subscribe to this mod's changes

palaia-memory is a skill published in the GitHub repository byte5ai/palaia (20 stars, last pushed 3d ago), licensed MIT. It adds 127 tokens to every session and 2,893 once invoked, about $0.0005 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.

Related

Other skills, from other repositories

setup

A setup guide for session-recall, a tool that lets an agent search and reuse information from earlier conversations. It covers installation, language, local or cloud processing, and optional team sharing.

AbsoluteMode/session-recall · 84 tokens

session-recall

Search the unified local history of past Claude Code, Codex, and Cursor sessions at the START of a task when the user references a prior bug, feature, decision, file, or piece of work. Use before assuming fresh context for prompts such as "remember when…", "we worked on…", "the X bug", "back to…", "what did we decide…

AbsoluteMode/session-recall · 92 tokens

memx

Use when an agent needs to recall, save, inspect, or audit memX memories through the bundled MCP tools.

NeoLi00/memX · 26 tokens

mission-control

Interact with Mission Control — AI agent orchestration dashboard. Use when registering agents, managing tasks, syncing skills, or querying agent/task status via MC APIs.

builderz-labs/mission-control · 34 tokens

memory-to-skill

Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…

zilliztech/memsearch · 82 tokens

remember-session

Use when the user asks to save, remember, record or persist what happened in the current session to MCP Memory Service ("save this session", "store the learnings", "vermerke es im Memory"), or when a session ends having produced decisions, root causes, or open follow-ups that a later session will need.

doobidoo/mcp-memory-service · 68 tokens