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-cleargit clone --depth 1 https://github.com/ukkit/memcordWrote 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/ukkit/memcord/memcord-clear)<a href="https://agentmods.dev/commands/ukkit/memcord/memcord-clear"><img src="https://agentmods.dev/badge/commands/ukkit/memcord/memcord-clear.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.00005 | $0.00126 |
| Opus 5 | $0.00003 | $0.00063 |
| Sonnet 5 | $0.00001 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
memcord-clear 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
Before clearing the conversation context:
- Check if there's an active memory slot (via memcord_status or by checking current state)
- If a slot is active:
- Ask the user if they want to save the conversation to memory before clearing
- If yes, use memcord_save_progress to auto-summarize and save
- Call memcord_close to deactivate the slot
- After saving and closing (or if user declines), inform them to run
/clear
Note: This command prepares for context clearing but does not execute /clear itself.
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 · 15 lines · 5 tokens per session scan A f55174ae71ee
memcord-clear is a command published in the GitHub repository ukkit/memcord (73 stars, last pushed 27d ago), licensed MIT. It adds 5 tokens to every session and 126 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
weekly
Weekly memory report — facts learned, procedures, repeated mistakes prevented.
compress
Save this Claude Code session to the vault and update the semantic memory index.
preserve
Scan this conversation and silently save anything worth permanent memory.
intel
Social media intelligence analysis — extract content from X posts or YouTube videos, analyze entities and insights, route to knowledge base and CRM.
memory-list
DEPRECATED: Use Serena listmemories instead. Lists recent memories from Forgetful with optional project filtering.
context
Search memories by keyword and show relevant context.