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 LovelaceLoom/grok-plugin-cc/plugin install grokWrote 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/lovelaceloom/grok-plugin-cc/memory)<a href="https://agentmods.dev/commands/lovelaceloom/grok-plugin-cc/memory"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/memory/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/commands/lovelaceloom/grok-plugin-cc/memory"><img src="https://agentmods.dev/badge/commands/lovelaceloom/grok-plugin-cc/memory.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.00011 | $0.00241 |
| Opus 5.5 | $0.00004 | $0.00096 |
| Sonnet 5.5 | $0.00002 | $0.00048 |
| Haiku 4.5 | $0.00001 | $0.00024 |
Grade A, and why
memory 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 1mo 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
Wrap grok memory. Grok's cross-session memory accumulates lessons across
calls (when enabled). Sub-actions:
/grok:memoryor/grok:memory stats— usage stats/grok:memory edit— open the memory store in an editor/grok:memory clear— wipe (be careful — irreversible)/grok:memory enable//grok:memory disable— toggle for this workspace
Per-call kill-switches are also available as flags on every command:
--no-memory (disable for one call) or --experimental-memory (enable for
one call, when not globally on). They're mutually exclusive.
Raw user input:
$ARGUMENTS
Run:
node "${CLAUDE_PLUGIN_ROOT}/scripts/companion.mjs" memory "$ARGUMENTS"
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.
- 1mo ago First seen · 28 lines · 11 tokens per session scan A f2f66d969d44
memory is a command published in the GitHub repository LovelaceLoom/grok-plugin-cc (5 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 241 once invoked, about $0.0000 per session on Opus 5.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
checkpoint
Write a new link in the continuum chain summarizing decisions/changes since the last link.
dream
Roll up the last N links into a single phase-digest link; originals move to archived/ (never deleted).
recall
Search past links in the continuum chain by tag/keyword and return matched summaries.
status
Show continuum chain health — link count, latest link, STATE.md size, archive usage, pending checkpoint.
comms-import
Back-fill old history from a WhatsApp "Export chat" .txt file — parsed, normalized, and reconciled into this repo's timeline by content fingerprint.
promote
Move .memory/ artifacts to permanent knowledge locations.