merge

A command for combining research claims from two independent sprints, where a sprint is a focused research project. It validates the incoming records, renames conflicting IDs, aligns topics, and finds disagreements or stronger evidence.

In plain words
What is it for?
Use it to import another sprint's claims file, review topic matches, detect conflicts and evidence upgrades, compile the merged records, and commit the result to Git.
Why use it?
It avoids manually rebuilding one research record and reduces errors when two teams studied the same question separately.

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/grainulation/wheat/merge
Clone the repo
git clone --depth 1 https://github.com/grainulation/wheat
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 383 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.00383
Opus 5 $0.00000 $0.00192
Sonnet 5 $0.00000 $0.00077
Haiku 4.5 $0.00000 $0.00038

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

Security

Grade A, and why

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

templates/commands/merge.md · 55 lines

What it actually says

/merge — Combine Claim Sets Across Sprints

You are merging claims from another sprint into the current one. This is for when two teams researched the same problem independently and need to combine their findings.

Process

  1. Parse the argument: The user provides a path to another sprint's claims.json.

    • Example: /merge ../auth-sprint/claims.json
    • If no path given, ask for it.
  2. Validate both claim sets:

    • Read the current claims.json
    • Read the incoming claims file
    • Validate both against the compiler schema:
      npx @grainulation/wheat compile --input <incoming-path> --output /tmp/wheat-merge-incoming.json
      
  3. Determine the sprint slug: Derive from the incoming sprint's meta.question.

  4. Resolve ID collisions: Prefix all incoming claim IDs with the sprint slug:

    • r001 -> auth-r001
    • Also update all conflicts_with and resolved_by references.
  5. Align topics: Present probable topic mappings for user confirmation.

  6. Detect cross-sprint conflicts and identify evidence upgrades.

  7. Write merged claims.json and compile:

    npx @grainulation/wheat compile --summary
    

Git commit

Commit: wheat: /merge <slug> — merged <N> claims from <source path>

Tell the user

  • How many claims were merged
  • Topic alignment results
  • Cross-sprint conflicts detected
  • Suggest: /resolve for conflicts, /blind-spot for cross-sprint gaps

Cleanup

rm -f /tmp/wheat-merge-*.json

$ARGUMENTS

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. 2d ago First seen · 55 lines · 0 tokens per session scan A 0009e5062927

Subscribe to this mod's changes

merge is a command published in the GitHub repository grainulation/wheat (20 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 383 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-30.