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/xzawed/claude-grok-build-plugin/memorygit clone --depth 1 https://github.com/xzawed/claude-grok-build-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/xzawed/claude-grok-build-plugin/memory)<a href="https://agentmods.dev/commands/xzawed/claude-grok-build-plugin/memory"><img src="https://agentmods.dev/badge/commands/xzawed/claude-grok-build-plugin/memory.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.00006 | $0.00381 |
| Opus 5 | $0.00003 | $0.00191 |
| Sonnet 5 | $0.00001 | $0.00076 |
| Haiku 4.5 | $0.00001 | $0.00038 |
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 today.
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
Call grok_cli with args starting ["memory", ...]. memory clear is the only
subcommand grok exposes — there is no list/search (grok memory list exits 2 with
unrecognized subcommand), so do not invent one. Memory is otherwise driven from grok's
own TUI (/memory …) and GROK_MEMORY=1, and lives under <grok home>/memory/.
memory clear is destructive and asks Are you sure? [y/N] before deleting. This wrapper
gives grok no stdin, so an unanswered prompt returns Cancelled. immediately rather than
hanging — but that also means the clear does nothing. Confirm the scope with the user
here, then pass -y, which is what actually performs the deletion:
["memory","clear","-y"]— workspace memory for the current directory (the default). This is not justMEMORY.md: it also deletessessions/andindex.sqlitefor that workspace, so prior session history goes with it. Say that before you send-y.["memory","clear","--global","-y"]— the globalMEMORY.md["memory","clear","--all","-y"]— both of the above
Never send -y on the user's behalf without them having asked for a clear: the flag is the
only thing standing between the request and permanent deletion.
Present stdoutTail; on error show stderrTail. If status is blocked, relay the
message. Note the reported billing (the configured mode, not an observed charge).
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.
- today Changed · +14 lines c93251df76bf
- 4d ago First seen · 12 lines · 6 tokens per session scan A 5fba813a9635
memory is a command published in the GitHub repository xzawed/claude-grok-build-plugin (1 stars, last pushed yesterday), licensed MIT. It adds 6 tokens to every session and 381 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
learn
Force claude-smart to extract learnings from this session now.
recall-save
Generate / overwrite .recall/context.md with Recall's local offline summarizer.
psql-query
Run ad-hoc PostgreSQL analytics queries against dev/test database.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.