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/zenetusken/consolidate-memory/cm-sharegit clone --depth 1 https://github.com/Zenetusken/consolidate-memoryWrote 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/zenetusken/consolidate-memory/cm-share)<a href="https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-share"><img src="https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-share.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.1 | $0.00033 | $0.00684 |
| Opus 5 | $0.00016 | $0.00342 |
| Sonnet 5 | $0.00007 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
cm-share 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
A single fact into the shared layer, with the dream's own verification discipline
(see docs/cm-commands-onboarding.spec.md §2.2). This is AUTHORING — the claim
must survive verification before it may exist. NO VERIFY, NO WRITE.
-
Read the single sources first (never paraphrase them):
${CLAUDE_PLUGIN_ROOT}/skills/consolidate-memory/references/harness-map.md§ "verification recipes", and the Phase-2 scope cascade in${CLAUDE_PLUGIN_ROOT}/skills/consolidate-memory/SKILL.md. -
Verify. Check the claim against THIS repo's live files/git with the recipes; for a
user-global/stack-generalscope, name at least one other existing project where it holds (G2.3). A claim that fails verification is reported and dropped, never written. -
Scope by content (the cascade, never vibes). A
project-localclaim does not belong here — point atcm local upsertinstead. -
Dedup. Grep the domain canonicals for the same content; a duplicate reconciles onto the existing fact, never a second copy.
-
Draft + show. Draft the fact (frontmatter + body) and SHOW it — including the before/after diff when the stem already exists (a replace freezes other projects' mirrors at their next pull). The user's confirmation is the gate. Groups (v0.4.10): when groups exist, ASK "share to a group or the whole domain?", and print the narrowing VERBATIM when a group is chosen — "delivery LIMITED to N members across X, Y; M same-domain projects STOP receiving it" — recipients narrow, never widen, and the exclusion is stated, never implied.
-
Write through the sole canonical writer — one journaled transact (canonical + catalog + registry + this project's mirror + pointer):
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py canonical upsert <stem> --file <draft-file> --origin --project .If the writer refuses with "recipients predate the current group — re-confirm (--repoint) or re-point": the draft's
recipients:cite a group RECREATED after the draft'scontent_modified— the group's identity is fresh and the citation is stale. When the user confirms the narrowing against the CURRENT group (step 5's confirmation IS the re-confirmation), re-run with--repointappended — the writer re-stamps the fact to now and accepts. Never hand-bumpcontent_modified.
Enrolled projects only (the writer refuses otherwise). A secret-shaped draft is
refused by the firewall — rephrase, never weaken it. A stack-general fact's
stacks: must be detectable; the writer's own error names the undetectable set.
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 First seen · 53 lines · 33 tokens per session scan A a2269f80217d
cm-share is a command published in the GitHub repository Zenetusken/consolidate-memory (6 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 684 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-09-05.
Other commands, from other repositories
remember
Explicitly save something to memory as an experience.
evolution
Show what the system learned and changed recently.
smartcompact
Pin important turns before compacting — pins survive compaction via SessionStart hook reinjection.
recall
Search verbatim history from previous Claude Code sessions.
reindex
Index the history of every project (one-time backfill).
topics
Recurring themes distinctive to this project.