Borrowing it
Nothing to install: this file belongs to matrixorigin/memoria. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/matrixorigin/memoria/main/.kiro/steering/memory-branching-patterns.mdgit clone --depth 1 https://github.com/matrixorigin/memoriaWrote 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/instructions/matrixorigin/memoria/memory-branching-patterns)<a href="https://agentmods.dev/instructions/matrixorigin/memoria/memory-branching-patterns"><img src="https://agentmods.dev/badge/instructions/matrixorigin/memoria/memory-branching-patterns/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.
<a href="https://agentmods.dev/instructions/matrixorigin/memoria/memory-branching-patterns"><img src="https://agentmods.dev/badge/instructions/matrixorigin/memoria/memory-branching-patterns.svg" alt="Reviewed on agentmods" width="80" 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.00992 | $0.00992 |
| Opus 5 | $0.00496 | $0.00496 |
| Sonnet 5 | $0.00198 | $0.00198 |
| Haiku 4.5 | $0.00099 | $0.00099 |
Grade A, and why
memory-branching 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.
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")
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 · 135 lines · 992 tokens per session scan A d1f340c89004
memory-branching is an instructions file published in the GitHub repository matrixorigin/memoria (596 stars, last pushed 2d ago), licensed Apache-2.0. It adds 992 tokens to every session, about $0.0050 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-08.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.