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/june9593/memarium-plugin/memariumnpx skills add june9593/memarium-plugin --skill memariumgit clone --depth 1 https://github.com/june9593/memarium-pluginWrote 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)<a href="https://agentmods.dev/skills/june9593/memarium-plugin/memarium"><img src="https://agentmods.dev/badge/skills/june9593/memarium-plugin/memarium.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.1 | $0.00131 | $0.08304 |
| Opus 5 | $0.00066 | $0.04152 |
| Sonnet 5 | $0.00026 | $0.01661 |
| Haiku 4.5 | $0.00013 | $0.00830 |
Grade A, and why
memarium 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 — 617 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/memarium — digest sessions into the typed Memory OS
This skill walks the in-session Claude (you) through digesting the user's
already-synced AI coding sessions into ONE per-project knowledge layer: typed
memory — episodic (one per work thread: the arc, dead-ends, decisions),
semantic (durable facts), procedural (how-to playbooks + gotchas), core
(never-forget rules) — plus the two derived layers, the entity wiki and
distilled Q&A. It is AI-native: agents read this via /memarium-recall and
the SessionStart primer. There is no human "book" — no chronicles, no topics, no
reading site.
Pure mechanical CLI handles I/O ("$VBP" prepare / "$VBP" memory-write /
"$VBP" memory-propose / "$VBP" entity-write / "$VBP" qa-write /
"$VBP" skip-write / "$VBP" finalize / "$VBP" list-projects); the LLM work —
segmentation + writing — is yours, in this conversation, with full context.
Inputs you assume
- The plugin's
orchestratestep (Pre-step + Step 0 below) scans the user's local Claude Code + Copilot Chat + Codex Desktop/interactive CLI JSONL, writes rendered.mdinto~/.memarium/session-repo/raw_sessions/..., and updates.memarium/index.json. You don't need to check whether sync ran — the plugin scans on every run. - If the user also installed the optional
memariumnpm CLI for cross-device sync, fine — both write the same spool. Don't gate on it; it's not required.
Step −1 — Locate the plugin binary (DO THIS FIRST OF ALL)
${CLAUDE_PLUGIN_ROOT} is not populated in your in-session Bash environment,
so discover the plugin's bin path and stash it in a shell variable:
VBP="${CLAUDE_PLUGIN_ROOT:+$CLAUDE_PLUGIN_ROOT/bin/memarium-plugin.js}"
[ -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-)
echo "VBP=$VBP"
Confirm it resolves (picks the highest semver version):
[ -x "$VBP" ] && "$VBP" --version
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +1 lines 76ed08f72932
- 5d ago First seen · 616 lines · 131 tokens per session scan A 1c052bac4dc4
memarium is a skill published in the GitHub repository june9593/memarium-plugin (1 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 8,304 once invoked, about $0.0007 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
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
cco-templates
Manage context templates for common task types.
knowledge-priming-refiner
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create…