A command for adding one verified fact to a shared memory store used across projects. It checks the claim against live repository files, shows the proposed change, and writes it only after user confirmation.

Use it to author a cross-project fact, check whether it already exists, review the proposed addition or replacement, and save it after approval.

It prevents unverified, local, or duplicate information from becoming shared guidance. The verification and review step helps keep shared project knowledge accurate.

cm-share — Command for Claude Code by Zenetusken/consolidate-memory

Install

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.

Claude Code

/plugin marketplace add Zenetusken/consolidate-memory

Claude Code

/plugin install consolidate-memory

Made for: Claude Code.

Or install consolidate-memory, the plugin that ships this one along with the rest of its 1 skill, 8 commands, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-share/github.svg)](https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-share)

Your own site

<a href="https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-share"><img src="https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-share/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.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 685 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00685
Opus 5.5	$0.00013	$0.00274
Sonnet 5.5	$0.00007	$0.00137
Haiku 4.5	$0.00003	$0.00068

Measured 1mo ago against content hash 604ece9483a9, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

plugins/consolidate-memory/commands/cm-share.md · 53 lines

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-general scope, 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-local claim does not belong here — point at cm local upsert instead.
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's content_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 --repoint appended — the writer re-stamps the fact to now and accepts. Never hand-bump content_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.

Changes

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 Changed 604ece9483a9
2mo ago First seen · 53 lines · 33 tokens per session scan A a2269f80217d

Subscribe to this mod's changes

cm-share is a command published in the GitHub repository Zenetusken/consolidate-memory (7 stars, last pushed 1mo ago), licensed MIT. It adds 33 tokens to every session and 685 once invoked, about $0.0001 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-09-05.

Claude Code Memory and context ai-agents claude-code-plugin context-management

cm-share next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cm-shareZenetusken/consolidate-memory	Command	7	1mo ago	MIT	A	33	Claude Code
remembrall-helpcukas/remembrall	Command	6	3d ago	MIT	A	17	Claude Code
budgetcukas/remembrall	Command	6	3d ago	MIT	A	13	Claude Code
handoffse4thvin/context-handoff	Command	1	5mo ago	MIT	A	14	Claude Code
recall-maintaindavegoldblatt/total-recall	Command	202	8mo ago	none	A	0	Claude Code
recall-init-idsdavegoldblatt/total-recall	Command	202	8mo ago	none	A	0	Claude Code
recall-initdavegoldblatt/total-recall	Command	202	8mo ago	none	A	0	Claude Code