Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add june9593/memarium-plugin/plugin install memariumWrote 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/june9593/memarium-plugin/memarium-recall)<a href="https://agentmods.dev/skills/june9593/memarium-plugin/memarium-recall"><img src="https://agentmods.dev/badge/skills/june9593/memarium-plugin/memarium-recall/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/june9593/memarium-plugin/memarium-recall"><img src="https://agentmods.dev/badge/skills/june9593/memarium-plugin/memarium-recall.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00333 | $0.02613 |
| Opus 5 | $0.00167 | $0.01307 |
| Sonnet 5 | $0.00067 | $0.00523 |
| Haiku 4.5 | $0.00033 | $0.00261 |
Grade A, and why
memarium-recall 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 2d 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memarium-recall — read your own notes before doing the work
You (in-session Claude) just landed in a project repo. The user has been
working in this repo (and others) for weeks/months, and the memarium plugin
has captured every Claude Code + Copilot + supported Codex session into ~/.memarium/session-repo/.
The /memarium digest distilled those sessions into typed memory —
episodic (the arc / dead-ends / decisions of a past work thread), semantic
(durable project facts), procedural (how-to playbooks + gotchas), core
(never-forget rules) — one AI-native, scored knowledge layer. (There is no
human "book" anymore.)
Your job here: before you explore code, run recall with your task keywords,
then Read the top 1–5 hits. Past-you may have already debugged exactly this.
Two-stage recall (low context by design)
| Stage | Payload | Question it answers |
|---|---|---|
| 1 (this command) | ranked hits — title + 1-line summary + whyRecalled per entry, bodies NOT loaded |
"Which past episodes/facts/procedures bear on my task?" |
2 (Read tool) |
full body, ~1–3 KB per entry | "What did past-me actually do / decide / hit here?" |
The CLI does the ranking (keyword overlap over title/summary/entities + file/commit overlap + recency + importance), so you don't triage a topic tree — you get a relevance-sorted list directly.
Step 0 — locate the plugin binary
VBP="${CLAUDE_PLUGIN_ROOT}/bin/memarium-plugin.js"
[ -n "${CLAUDE_PLUGIN_ROOT}" ] && [ -x "$VBP" ] || VBP=$(ls -d ~/.claude/plugins/cache/*/memarium/*/bin/memarium-plugin.js 2>/dev/null | awk -F/ '{print $(NF-2)"\t"$(0)}' | sort -V | tail -1 | cut -f2-)
[ -x "$VBP" ] && "$VBP" --version
The skill loader substitutes ${CLAUDE_PLUGIN_ROOT} with this plugin's
installation directory. If that root is unavailable, the fallback selects the
highest cached semver, regardless of marketplace name or directory mtime.
Bash calls do not share shell variables. Run discovery and the first CLI
command in the same Bash call. For later calls, use the resolved absolute binary
path (quoted), or repeat discovery; do not assume $VBP is still set.
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.
- 2d ago Changed · +8 lines 6e0393f30115
- 5d ago Changed df607a22ee7e
- 9d ago First seen · 165 lines · 333 tokens per session scan A 9669e67d4da1
memarium-recall is a skill published in the GitHub repository june9593/memarium-plugin (1 stars, last pushed 2d ago), licensed MIT. It adds 333 tokens to every session and 2,613 once invoked, about $0.0017 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
ucai-patterns
Use when the user asks about Claude Code best practices, how to write agents, how to use hooks, how to manage context, or how to work effectively with Claude Code's native systems.
memory-curator
Use at session-close when a session captured several new memories, or on-demand, to consolidate, deduplicate, prune, and structure the beads memory store. Triggers on "curate memories", "clean up memories", "memory sweep".
orient
Use when user invokes /orient with a topic keyword, entity type, project name, time qualifier, or combination. Also triggers on "what do we know about X", "remind me about X", "where did we leave off on X". Provides targeted context loading — searches the MCP Memory Server graph, knowledge files, journal entries, and…
memory
Use when user invokes /memory with a subcommand (search, trace, add, episode, status). Also triggers on "search my memory for X", "add to memory", "what do I know about X" (when membrain is available), "memory status", "memory trace". Searches and manages the membrain knowledge graph via MCP tools or HTTP API.
capture
Use when user invokes /capture to capture information from the current conversation into a staging file for later reflection and knowledge graph processing. Accepts no arguments (auto-extract), specific facts as text, or filter keywords like "decisions" or "technical". Do NOT use when the user wants to write directly…
lembas
Use between workflow phases or when context feels bloated. Writes a structured checkpoint capturing task, findings, files, state, and next steps, then continues from that summary instead of the full history. Invoke standalone or automatically between quest phases.