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/lolaplex/agents-memory/memory-distillnpx skills add Lolaplex/agents-memory --skill memory-distillgit clone --depth 1 https://github.com/Lolaplex/agents-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/lolaplex/agents-memory/memory-distill)<a href="https://agentmods.dev/skills/lolaplex/agents-memory/memory-distill"><img src="https://agentmods.dev/badge/skills/lolaplex/agents-memory/memory-distill.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.00076 | $0.00574 |
| Opus 5 | $0.00038 | $0.00287 |
| Sonnet 5 | $0.00015 | $0.00115 |
| Haiku 4.5 | $0.00008 | $0.00057 |
Grade A, and why
memory-distill 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 3d 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.
What it actually says
memory-distill
Staging inbox is temporary — from any ingest source (staging/ingest/<id>/captured.md) or project/user staging. Distill durable facts into typed paths; discard ephemeral noise.
When staging inbox depth reaches staging_nag_threshold (default 50), agents automatically receive a nag alert in AGENTS.md and MCP tool responses to trigger distillation.
Quick Option: Auto-Distill
For fast automated triage of noise and standard facts:
- Call MCP
auto_distill(limit=50, discard_noise=true) - Or CLI:
python -m agents_memory distill --auto
Full LLM Workflow
- Call MCP
get_staging_inbox(limit=20)— returns groups by source (ingest id / file). - For each bullet in each group, evaluate:
- Keep (Durable Fact): Core decisions, tech stack choices, preferences, personal workflow rules, durable architecture constraints.
- Select target
kind:concept,entity,workflow,note,project,decision,proposed,implemented. - Assign clean slug
name(andproject/collectionif applicable).
- Select target
- Discard (Noise / Ephemeral): One-off debug talk, temporary questions, code snippets with no lasting rule, accidental transcript dumps.
- Keep (Durable Fact): Core decisions, tech stack choices, preferences, personal workflow rules, durable architecture constraints.
- Call MCP
distill_batch(items_json)with the classified items. Always pass throughsource_path(andprojectwhen present) from the inbox item so removal hits the right file:[ { "bullet": "[Homelab @ …] Always use Tailwind v3", "kind": "note", "name": "stack", "project": "customs", "source_path": "user/staging/ingest/cursor/captured.md" }, { "bullet": "Can you check line 40 of main.py", "discard": true, "source_path": "user/staging/ingest/cursor/captured.md" } ] - Repeat until
get_staging_inboxreports"total": 0. distill_batchandpromote_bulletautomatically sync to all IDEs/CLIs upon completion.
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.
- 3d ago First seen · 45 lines · 76 tokens per session scan A 04c9cd453c80
memory-distill is a skill published in the GitHub repository Lolaplex/agents-memory (3 stars, last pushed 3d ago), licensed MIT. It adds 76 tokens to every session and 574 once invoked, about $0.0004 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-31.
Other skills, from other repositories
On_Board
Skill "On_Board" from swisspra/On_Board, covering greetings agents!, welcome on board — agent shared memory skill.md, ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━, drop into any project that uses on board mcp and via native instruction file system.
memory-curation
When you have read / processed a workspace asset in this session and learned something durable about it, write a memory page so future sessions benefit. Maintain the workspace wiki's hierarchical structure as it grows.
memory
Persist and retrieve agent memory across sessions — write durable notes, read by path, recall via semantic search, list/delete, and consolidate. Use whenever the user asks to remember/forget something, when you need to look up past decisions or context, or when episodic state matters beyond the current turn. Executes…
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.
dashboard
Open OwnMem Console, the local dashboard for this repository's memory. Use when the user asks to open the dashboard, see memory metrics, check adoption or recall quality, or set up the optional embedding lane. Requires a repository initialized with the dashboard layer.
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.