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 agentmods add skills/phasespace-labs/palinode/palinode-memorynpx skills add phasespace-labs/palinode --skill palinode-memorygit clone --depth 1 https://github.com/phasespace-labs/palinodeWrote 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/phasespace-labs/palinode/palinode-memory)<a href="https://agentmods.dev/skills/phasespace-labs/palinode/palinode-memory"><img src="https://agentmods.dev/badge/skills/phasespace-labs/palinode/palinode-memory.svg" alt="Measured on agentmods" 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 | $0.00141 | $0.01027 |
| Opus 5 | $0.00071 | $0.00513 |
| Sonnet 5 | $0.00028 | $0.00205 |
| Haiku 4.5 | $0.00014 | $0.00103 |
Grade A, and why
palinode-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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Palinode Memory
Palinode stores typed memory as git-versioned markdown files with hybrid search (BM25 + vector). This skill provides procedural guidance for using Palinode's tools effectively.
Core Tools
| Tool | When to Use |
|---|---|
palinode_search |
Find relevant memories by meaning or keyword |
palinode_save |
Store a new typed memory (person, project, decision, insight) |
palinode_status |
Show file counts, chunk counts, entity graph, system health |
palinode_trigger |
Register an intention — auto-surfaces a memory file when context matches |
palinode_diff |
See what changed in a memory file recently |
palinode_consolidate |
Run or check the weekly compaction job |
Memory Types
Use the right type when saving:
PersonMemory— facts about a person (name, role, preferences, context)Decision— architectural/product decisions with rationaleProjectSnapshot— current state of a project (milestone, blockers, next)Insight— generalizable lessons learned (applies beyond current project)ActionItem— follow-up task with owner and deadline
Search Effectively
Palinode uses 4-phase injection — you don't always need to search manually:
- Core files (
core: true) are always injected at session start - Topic search runs on every turn automatically
- Associative recall expands entity mentions automatically
- Triggers fire when registered contexts match
Only call palinode_search explicitly when you need something specific not surfaced by injection, or when the user asks "what do I know about X?"
Saving Memories
Guidelines:
- Save decisions with rationale — not just what was decided, but why
- Save people context when you learn preferences, constraints, or relationships
- Save insights when a lesson applies broadly (not just to one task)
- Don't save raw conversation transcript — save the distilled fact
Example save calls:
palinode_save(
content="Alice and Bob are co-founders, 3-year gap in joining. CEO role is shared.",
type="PersonMemory",
entities=["person/alice", "project/my-app"]
)
palinode_save(
content="Curation > volume for training data. 90 curated samples >> 1,623 raw.",
type="Insight",
entities=["project/my-app"]
)
What ships with it
1 file beside SKILL.md 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.
- 4d ago First seen · 105 lines · 141 tokens per session scan A b230610718ab
palinode-memory is a skill published in the GitHub repository phasespace-labs/palinode (35 stars, last pushed today), licensed MIT. It adds 141 tokens to every session and 1,027 once invoked, about $0.0007 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
kayba-ace
This skill ships learnfromtraces.py, a script that reads OpenClaw session transcripts, feeds them through the ACE learning pipeline, and writes an updated skillbook to disk.
plur-memory
Persistent learning for AI agents. Open engram format. Your agent learns from corrections, remembers across sessions, and transfers knowledge across domains.
plur-memory
Your memory stays on your machine. No cloud, no tracking, no API key. PLUR makes your OpenClaw remember — and shares that memory with every other tool you use.
lemmalog
Externalize working memory and logical state into the lemmalog Datalog engine (MCP). Use for ANY multi-step task where state should outlive one context window or span agents: long investigations, debugging sessions, audits, multi-agent searches, systematic explorations, planning with many interdependent constraints…
honcho-integration
Integrate Honcho memory into existing Python or TypeScript codebases. Use when adding Honcho SDK, setting up peers, configuring sessions, and accessing Honcho's representation.
honcho-memory
Concepts and strategy for using a connected Honcho as persistent memory of the user — the recall/record loop and session and peer design. Start here to understand how Honcho memory works, then connect — via a first-class integration for your environment if one exists (preferred), or raw MCP tools (covered here) or the…