What is memory-branching-patterns?

A set of patterns for using Memoria's branch-like memory copies to test ideas and changes separately from the main memory.

Use it to compare technologies, try memory refactors, review differences, then merge accepted changes or delete failed experiments.

It keeps experiments and risky memory edits from changing trusted information until you decide to merge them.

memory-branching-patterns — Cursor rule by matrixorigin

Install

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.

agentmods

npx agentmods add rules/matrixorigin/memoria/memory-branching-patterns

Clone the repo

git clone --depth 1 https://github.com/matrixorigin/memoria

Made for: Cursor.

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

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

Security scan A 0 findings. Scan, not verified.

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	$0.00018	$0.00983
Opus 5	$0.00009	$0.00491
Sonnet 5	$0.00004	$0.00197
Haiku 4.5	$0.00002	$0.00098

Measured yesterday against content hash 019a220d0dc5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

memory-branching-patterns 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 yesterday.

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.

.cursor/rules/memory-branching-patterns.mdc · 135 lines

How it starts

The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Memory Branching Patterns

Use Memoria's Git-like branching to isolate experiments, evaluate alternatives, and protect stable memory state.

Pattern 1: Tech Evaluation

Compare alternatives without polluting main memory.

memory_branch(name="eval_[technology]")
memory_checkout(name="eval_[technology]")

# Store findings on branch
memory_store(content="[technology] evaluation: [findings]", memory_type="semantic")

# When done — preview and decide
memory_diff(source="eval_[technology]")

# Accept: merge back
memory_checkout(name="main")
memory_merge(source="eval_[technology]", strategy="replace")
memory_branch_delete(name="eval_[technology]")

# Reject: just delete
memory_checkout(name="main")
memory_branch_delete(name="eval_[technology]")

Pattern 2: Pre-Refactor Safety Net

Snapshot + branch before risky memory changes.

memory_snapshot(name="pre_[task]", description="before [task]")
memory_branch(name="refactor_[task]")
memory_checkout(name="refactor_[task]")

# Do risky work on branch...

# If it goes wrong:
memory_checkout(name="main")
memory_branch_delete(name="refactor_[task]")
# main is untouched

# If it succeeds:
memory_diff(source="refactor_[task]")
memory_checkout(name="main")
memory_merge(source="refactor_[task]")  # default strategy: branch wins on conflicts
memory_branch_delete(name="refactor_[task]")

Pattern 3: A/B Memory Comparison

Two branches for competing approaches, diff both before deciding.

memory_branch(name="approach_a")
memory_branch(name="approach_b")

# Work on A
memory_checkout(name="approach_a")
memory_store(content="Approach A: [details]", memory_type="semantic")

# Work on B
memory_checkout(name="approach_b")
memory_store(content="Approach B: [details]", memory_type="semantic")

# Compare
memory_diff(source="approach_a")
memory_diff(source="approach_b")

# Merge winner, delete both
memory_checkout(name="main")
memory_merge(source="approach_a")  # default strategy: branch wins on conflicts
memory_branch_delete(name="approach_a")
memory_branch_delete(name="approach_b")

Read the full file on GitHub · 135 lines

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.

yesterday First seen · 135 lines · 18 tokens per session scan A 019a220d0dc5

Subscribe to this mod's changes

memory-branching-patterns is a cursor rule published in the GitHub repository matrixorigin/memoria (591 stars, last pushed 6d ago), licensed Apache-2.0. It adds 18 tokens to every session and 983 once invoked, about $0.0001 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.

Code review LLM Memory and context Testing agent ai storage

memory-branching-patterns

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Memory Branching Patterns

Pattern 1: Tech Evaluation

Pattern 2: Pre-Refactor Safety Net

Pattern 3: A/B Memory Comparison

What this file has done since we first saw it

Other cursor rules, from other repositories

internationalization

frontend-architecture

turborepo

lean

react_hooks

tdd