branch.merge

branch.merge is a command for coding agents from stratalab/strata-core. It costs 0 tokens per session (267 once invoked), scanned A, original, Apache-2.0.

A branch merge applies one branch's changes to another as one commit. A commit is a recorded group of database changes; the source branch stays unchanged.

In plain words
What is it for?
Use it to promote key-value, JSON, or vector changes into a target branch. Event streams and graphs can be compared but are not merged.
Why use it?
It combines work from an isolated branch while detecting conflicting edits. By default, conflicting changes stop the merge without changing either branch.

Command

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 commands/stratalab/strata-core/branch.merge
Clone the repo
git clone --depth 1 https://github.com/stratalab/strata-core

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.

agentmods badge for branch.merge

README.md
[![agentmods](https://agentmods.dev/badge/commands/stratalab/strata-core/branch.merge.svg)](https://agentmods.dev/commands/stratalab/strata-core/branch.merge)
Your own site
<a href="https://agentmods.dev/commands/stratalab/strata-core/branch.merge"><img src="https://agentmods.dev/badge/commands/stratalab/strata-core/branch.merge.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 267 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00267
Opus 5 $0.00000 $0.00133
Sonnet 5 $0.00000 $0.00053
Haiku 4.5 $0.00000 $0.00027

Measured 4d ago against content hash aca3c52a223c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

crates/executor/idl/v1/prose/commands/branch.merge.md · 26 lines

What it actually says

Promotes the source branch's changes into the target branch as a single atomic commit, leaving the source unchanged. The branch point is derived from the recorded fork lineage, and a three-way merge applies every change the source made since that point.

Merge applies to key-value, JSON, and vector data. Event streams and graphs are compared (see branch.diff) but never merged — divergent append-only and structural data cannot be three-way merged — so a promotion leaves them untouched.

The strict strategy (the default) refuses with conflict.engine.promotion, mutating nothing, when the two branches changed the same entity differently since the branch point. The source_wins strategy applies the source side's value or tombstone for each such conflict and reports every overwritten or deleted target entry. A promotion that applies nothing writes no commit and leaves the target unchanged.

Branches with no shared fork lineage are rejected with invalid_argument.engine.branch_point; a missing branch with not_found.engine.branch.

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.

  1. 4d ago First seen · 26 lines · 0 tokens per session scan A aca3c52a223c

Subscribe to this mod's changes

branch.merge is a command published in the GitHub repository stratalab/strata-core (2 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 267 tokens. 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-31.