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/runtimenoteslabs/memory-layer/memoriesgit clone --depth 1 https://github.com/runtimenoteslabs/memory-layerWrote 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/runtimenoteslabs/memory-layer/memories)<a href="https://agentmods.dev/commands/runtimenoteslabs/memory-layer/memories"><img src="https://agentmods.dev/badge/commands/runtimenoteslabs/memory-layer/memories.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.00004 | $0.00201 |
| Opus 5 | $0.00002 | $0.00101 |
| Sonnet 5 | $0.00001 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
memories 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
Memories Command
List all memories stored in the Memory Layer.
Usage
/memories [--limit N] [--category <cat>]
Options
| Option | Description | Default |
|---|---|---|
--limit N |
Maximum number of results | 20 |
--category <cat> |
Filter by category | all |
Examples
# List all memories
/memories
# List with limit
/memories --limit 10
# List only gotchas
/memories --category gotcha
Implementation
List memories via CLI:
mem list --limit 20
Output
Shows each memory with:
- Memory ID (for use with
/outcomeor/forget) - Category
- Content preview
- Outcome score (if feedback received)
- Created date
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 · 52 lines · 4 tokens per session scan A b6ef7ab78d36
memories is a command published in the GitHub repository runtimenoteslabs/memory-layer (10 stars, last pushed 3mo ago), licensed MIT. It adds 4 tokens to every session and 201 once invoked, about $0.0000 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 commands, from other repositories
memory-status
Check the Pseudolife-MCP memory daemon and report bank health.
dream
Copy to .claude/commands/dream.md in any project to get /dream. -->.
ov
Show OpenViking memory plugin status — server, identity, last injection / recall, toggles.
weekly
Weekly memory report — facts learned, procedures, repeated mistakes prevented.
dream
Memory dream pass — judge undreamed days, promote durable signal to long-term, then sweep.
tree-ring-update
Check for or install a verified Tree Ring Memory CLI update without changing installation scope.