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/plur-ai/plur/plur-session-endnpx skills add plur-ai/plur --skill plur-session-endgit clone --depth 1 https://github.com/plur-ai/plurWhat 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.00035 | $0.00950 |
| Opus 5 | $0.00017 | $0.00475 |
| Sonnet 5 | $0.00007 | $0.00190 |
| Haiku 4.5 | $0.00003 | $0.00095 |
Grade A, and why
plur-session-end 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.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PLUR Session End
Run this at the end of a conversation to extract what is worth remembering.
PLUR stores durable knowledge — corrections, conventions, preferences, decisions. It does not store session logs, one-off status, or anything that will be irrelevant next week. This skill enforces that discipline.
When to Use
- The user says "wrap up", "end session", "we're done", or similar
- The conversation is winding down after completing a task
- You want to record what you learned before the context window closes
Procedure
Step 1 — Identify learning candidates
Scan the conversation for:
| Category | Examples |
|---|---|
| Corrections | "No, the API returns snake_case" / "Don't use X, use Y" |
| Preferences | "Always run lint before committing" / "User prefers concise explanations" |
| Codebase conventions | "This project uses repository pattern" / "Tests live in __tests__/" |
| Decisions | "We chose PostgreSQL for ACID compliance" |
| Gotchas | "The staging env needs NODE_ENV=staging, not production" |
| Terminology | "They call it a 'slot' not a 'channel'" |
Step 2 — Filter ruthlessly
Skip:
- Anything already obvious from reading the codebase
- Session-specific state ("we're working on the login page right now")
- One-off status ("the build was red this morning")
- Anything you are not confident about
- Secrets, credentials, API keys — never
Step 3 — Write each learning as a durable assertion
Format: a single clear statement that will make sense to a future agent with no session context.
Good: "The publish script requires npm 2FA — always run 'npm publish' interactively, never from CI."
Bad: "We talked about the publish issue."
Step 4 — Assign metadata
For each learning, determine:
type:correction|preference|convention|decision|gotcha|factdomain: the project, library, or topic area (e.g.,"plur","typescript","project:acme")scope: the scope of applicability (e.g.,"global","project:acme")tags: 2–5 descriptive tags
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 · 111 lines · 35 tokens per session scan A 5679a2e7e92e
plur-session-end is a skill published in the GitHub repository plur-ai/plur (243 stars, last pushed 2d ago), licensed Apache-2.0. It adds 35 tokens to every session and 950 once invoked, about $0.0002 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
membrain
Shared long-term memory over MCP. Call memorycontext once at the start of any session/task to load what is already known; use searchmemory before answering questions about the user or their projects; save durable facts, preferences, and decisions with savememory / savememories. All agents and the user share the same…
recall
Recall this repository's OwnMem local memory before changing code, and keep it healthy. Use when a repository contains .ownmem/, when past debugging lessons could apply ("have we hit this before", "why is it done this way"), or when the user mentions ownmem, project memory, or recalling across sessions.
mnemo-cortex
Installs and wires Mnemo Cortex (local-first persistent memory) into OpenClaw and other MCP-capable agents. Use for cross-session recall, decision history, or multi-agent shared memory.
init
Install or update OwnMem in the current repository. Use when the user asks to set up OwnMem, add local project memory for coding agents, or refresh an existing OwnMem installation after a version bump.
ogham-research
Structured memory capture for Ogham shared memory. Use when the user wants to store findings, remember something, save what was learned, or capture a decision. Triggers on "remember this", "store this", "save this finding", "save what we learned", "capture this decision", "log this", or any request to persist…
add-memory-system
Research and integrate a new agent-memory repository into Agent Memory Atlas. Use when asked to add, analyze, catalog, or compare a memory system in this repository, including its commit-pinned system report, comparative overview coverage, homepage card, generated site, and validation.