A command for connecting two repositories to a shared memory store. It checks both repositories, asks for explicit permission to enroll them, and can transfer a shared fact between them.

Use it to inspect enrollment status, plan and confirm access for both repositories, and complete cross-project memory setup.

It prevents repositories from being connected or changing domains without the operator's approval. It also makes partial setup recoverable instead of silently overwriting state.

cm-connect — 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-connect/github.svg)](https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-connect)

Your own site

<a href="https://agentmods.dev/commands/zenetusken/consolidate-memory/cm-connect"><img src="https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-connect/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-connect"><img src="https://agentmods.dev/badge/commands/zenetusken/consolidate-memory/cm-connect.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 616 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.00038	$0.00616
Opus 5.5	$0.00015	$0.00246
Sonnet 5.5	$0.00008	$0.00123
Haiku 4.5	$0.00004	$0.00062

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

Security

Grade A, and why

cm-connect 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-connect.md · 53 lines

What it actually says

The two-repo onboarding wizard (see docs/cm-commands-onboarding.spec.md). Enrollment is an OPERATOR grant (ADR 008) — this command sequences the grants, never self-grants; every enrollment is planned and confirmed.

Survey (read-only). Pre-flight the environment, then doctor both repos and show the plan — enrolled? domain? — plus each enrollment's forecast (how many unadmitted mirrors it would quarantine; quarantine is recoverable, never delete):
```
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/preflight.py" .   # exit 2 = fix the FAILs first
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py" doctor .
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py" doctor "<other-repo>"
```
Grants. For each unenrolled repo, show its plan and ask the user for ONE confirmation covering both. Apply each with its exact phrase (the confirmation is the grant):
```
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py" project enroll . --domain personal --apply --confirm enroll-personal
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/cm_ops.py" project enroll "<other-repo>" --domain personal --apply --confirm enroll-personal
```
A repo enrolled in a DIFFERENT domain is never auto-switched — point at move-domain. A failed second enroll leaves a valid partial state; re-running this command completes it (enroll is idempotent).
Share (optional). Ask for one claim sentence; if given, run /cm-share from this repo. Skip cleanly with "link only".

Absorb. Pull + harvest in BOTH repos — each picks up the domain facts it was missing:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --list .
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --pull .
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --harvest .
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --pull "<other-repo>"
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --harvest "<other-repo>"

Payoff. Show the network view — the links made:

python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --tokens .
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/sync_global.py" --network .

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 b933c951c513
2mo ago Changed · +1 lines befe661e2eda
2mo ago First seen · 52 lines · 38 tokens per session scan A 424b1758f06d

Subscribe to this mod's changes

cm-connect is a command published in the GitHub repository Zenetusken/consolidate-memory (7 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 616 once invoked, about $0.0002 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 Git and workflow Memory and context ai-agents claude-code-plugin context-management

cm-connect next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cm-connectZenetusken/consolidate-memory	Command	7	1mo ago	MIT	A	38	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
resumevikcena01/ai-continuity-plugin	Command	5	12d ago	MIT	A	20	Claude Code
handoffhautc-it/cil	Command	1	3mo ago	MIT	A	31	Claude Code
my_commitanilcancakir/claude-code-plugins	Command	5	9mo ago	MIT	A	29	Claude Code
handoffse4thvin/context-handoff	Command	1	5mo ago	MIT	A	14	Claude Code