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/june9593/memarium-plugin/memarium-contextgit 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/commands/june9593/memarium-plugin/memarium-context)<a href="https://agentmods.dev/commands/june9593/memarium-plugin/memarium-context"><img src="https://agentmods.dev/badge/commands/june9593/memarium-plugin/memarium-context.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.00032 | $0.00105 |
| Opus 5 | $0.00016 | $0.00053 |
| Sonnet 5 | $0.00006 | $0.00021 |
| Haiku 4.5 | $0.00003 | $0.00011 |
Grade A, and why
memarium-context 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 4d 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
Invoke the memarium-context skill via the Skill tool with skill: "memarium:memarium-context".
Run this at the START of work in a project repo (before exploring code). It loads the project's accumulated memory — architecture, setup, gotchas, rules — so you don't re-learn the codebase.
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.
- 4d ago First seen · 8 lines · 32 tokens per session scan A 4d6b4fbf3931
memarium-context is a command published in the GitHub repository june9593/memarium-plugin (1 stars, last pushed today), licensed MIT. It adds 32 tokens to every session and 105 once invoked, about $0.0002 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
learn
Force claude-smart to extract learnings from this session now.
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
show
Show this project's saved Recall context (.recall/context.md).
coding-drill
Rapid-fire reps — pattern recognition, complexity-of-this-snippet, template recall — flashcard cadence; prioritizes your weak patterns.
init
Bootstrap project context (project.intent.md and project.glossary.json) from an existing codebase using deterministic scan + LLM synthesis + interactive editing. Use --harness to scaffold additional repo-level harness docs.
ai-act-ask
Answer an EU AI Act question grounded in the bundled knowledge base — verbatim statute text, obligation paraphrases, and the compound-risk taxonomy. Offline and deterministic by default; cites the articles it relies on.