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.
/plugin marketplace add byte5ai/palaianpx agentmods add plugins/byte5ai/palaia/clientsgit clone --depth 1 https://github.com/byte5ai/palaiaGrade 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 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.
What it actually says
{
"name": "palaia-memory",
"description": "Makes an agent use palaia's shared memory without being told, and work alongside other agent sessions: when to recall, how to resume work, what deserves capturing, and when to register, check in and reply.",
"version": "0.1.0",
"author": {
"name": "byte5",
"url": "https://github.com/byte5ai/palaia"
},
"homepage": "https://github.com/byte5ai/palaia/tree/main/v3/clients",
"repository": "https://github.com/byte5ai/palaia",
"license": "MIT",
"keywords": ["memory", "mcp", "recall", "capture", "messaging", "palaia"]
}
What ships with it
1 file beside plugin.json 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 · 14 lines scan A 52f9c7d88f04
palaia-memory is a plugin published in the GitHub repository byte5ai/palaia (19 stars, last pushed 5d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
memX
memX: local-first semantic memory for coding agents. Native Claude Code lifecycle hooks.
session-recall-marketplace
Local shared-memory plugin for Claude Code, Codex, and Cursor sessions.
session-recall
Shared semantic recall over local Claude Code, Codex, and Cursor history. Bundles MCP search tools, deep recall, guided setup, and a background freshness hook.
silicon-circle
Agent client for Silicon Circle task trading and reviewed Skill commerce: publish or deliver work, consign or buy Skills, run hosted capabilities, use Circle Credits, and withdraw cleared earnings.
context-mem
The highest-accuracy memory system for AI agents — 100% retrieval on LongMemEval. 14 content-aware summarizers, hybrid search (BM25 + vector + LLM judge), entity intelligence, decision trails. Fully local, zero cost.
nextjs
Official Next.js skills: adopt and optimize Cache Components, adopt Partial Prefetching, and verify runtime behavior against a running dev server.