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/ukkit/memcord/memcord-save-progressgit clone --depth 1 https://github.com/ukkit/memcordWhat 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.00008 | $0.00121 |
| Opus 5 | $0.00004 | $0.00060 |
| Sonnet 5 | $0.00002 | $0.00024 |
| Haiku 4.5 | $0.00001 | $0.00012 |
Grade A, and why
memcord-save-progress 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 3d 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
Auto-summarize and save current conversation progress.
Use the memcord_save_progress tool to automatically summarize and append the current conversation to the memory slot.
Auto-detection is built-in: The server automatically detects the slot in this priority order:
- Explicit slot_name in arguments
- Currently active slot (via memcord_use/memcord_name)
- Project binding (
.memcordfile in current working directory)
Just call memcord_save_progress directly - do NOT manually search for .memcord files.
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.
- 3d ago First seen · 14 lines · 8 tokens per session scan A 64059f0cb72c
memcord-save-progress is a command published in the GitHub repository ukkit/memcord (72 stars, last pushed 26d ago), licensed MIT. It adds 8 tokens to every session and 121 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-30.
Other commands, from other repositories
compress
Save this Claude Code session to the vault and update the semantic memory index.
checkpoint
Save a mid-session checkpoint — for continuity between sessions of the same day.
resume
Load context from the vault before starting work.
preserve
Scan this conversation and silently save anything worth permanent memory.
update-model
Change an OpenClaw model configuration — with mandatory discovery, provider-aware validation, and 5-step verification. Designed to prevent every class of model configuration error.
fleet-announce
Announce a fleet update to users — send a personalized message from each person's bot explaining what changed and why they should care.