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 commands/simple4uhq/sae4u-memory/memory-distillgit clone --depth 1 https://github.com/Simple4uhq/sae4u-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/commands/simple4uhq/sae4u-memory/memory-distill)<a href="https://agentmods.dev/commands/simple4uhq/sae4u-memory/memory-distill"><img src="https://agentmods.dev/badge/commands/simple4uhq/sae4u-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.00000 | $0.00670 |
| Opus 5 | $0.00000 | $0.00335 |
| Sonnet 5 | $0.00000 | $0.00134 |
| Haiku 4.5 | $0.00000 | $0.00067 |
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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memory-distill — weekly memory cleanup
A periodic ritual: read the rolling tick log, propose promotions to permanent memory, and let the user confirm what to keep, archive, or forget.
When to run
- Weekly (e.g. Sunday evening or Monday morning).
- After heavy context-creation periods (a sprint close, a launch).
- When tick log files have piled up beyond what a quick scan can digest (~5+ days of unmerged ticks).
What it does
- Read the tick logs — all files under
~/.sae4u-memory/tick/that haven't been distilled yet, plus any new permanent files added since last distill. - Cluster by topic (use the 4 types — user/feedback/project/ reference — as a first cut, then group within type by topic).
- Propose actions for each cluster. Three outcomes per item:
- Promote to a permanent file (new or merge into existing). Update MEMORY.md.
- Drop — was tick-only noise; not worth keeping.
- Keep in tick log — borderline; see again next week.
- Surface for confirmation. The user reviews the proposals
and accepts / rejects each. Never auto-promote, never
auto-forget — see
rules/memory-cleanup-interactive.md. - Apply the confirmed actions:
- Move tick entries to permanent files
- Update MEMORY.md index
- Archive distilled tick log file (e.g. rename to
tick/distilled/2026-05-07.mdor compress)
- Stale check for permanent memory — entries not referenced in N weeks. Ask: "still interesting or forget?" Don't volunteer to delete; just surface the question.
How the AI presents this
Group by topic, not by file. The user shouldn't have to read 40 individual proposals — bundle related ticks into "here are 5 things about X, what shape do you want them in?"
Keep the proposals concrete:
Topic: testing approach
Across 4 ticks last week:
- 2026-05-02 — "don't mock the database in integration tests"
- 2026-05-04 — confirmed "TDD for new API endpoints"
- 2026-05-05 — "use testcontainers for postgres in CI"
- 2026-05-06 — "snapshot tests OK for component output"
Propose: promote to
feedback_testing_approach.mdconsolidating all four. Drop the per-tick entries from tick log.Accept / Reject?
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 · 72 lines · 0 tokens per session scan A a755bb8ebdf3
memory-distill is a command published in the GitHub repository Simple4uhq/sae4u-memory (0 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 670 tokens. 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 commands, from other repositories
mempalace-init
Set up MemPalace — install the package, initialize a palace, register the MCP server with Cursor, and verify everything works.
mempalace-status
Show the current state of your memory palace — wings, rooms, drawer counts, and suggestions.
ingest
Ingest source material into an active wiki. Accepts URLs, file paths, PDFs, freeform text, or processes the inbox. Supports tweets via Grok MCP.
fire-debug
Systematic debugging with persistent state, skills library integration, and WARRIOR validation.
review
Review the current diff against project memory.
speckit.archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.