swarm: Command for Claude Code

.claude/commands/merge_session.md

merge_session is a command for Claude Code from swarm-ai-research/swarm. It costs 0 tokens per session (1,231 once invoked), scanned A, original, MIT.

A command for bringing work from a separate Git session branch into the main branch. It uses rebase and fast-forward push, and can process one session or all session branches.

In plain words
What is it for?
Merging the current session, batch-merging all session branches, and optionally removing merged worktrees and branches.
Why use it?
It reduces the manual steps involved in combining isolated work, while checking that the branch and working tree are suitable.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

This is swarm-ai-research/swarm's own configuration. It tells Claude Code how to work on swarm itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything swarm configures →

Reuse

Borrowing it

Nothing to install: this file belongs to swarm-ai-research/swarm. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/merge_session.md
Clone the repo
git clone --depth 1 https://github.com/swarm-ai-research/swarm

Made for: Claude Code.

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 merge_session

README.md
[![agentmods](https://agentmods.dev/badge/commands/swarm-ai-research/swarm/merge_session/github.svg)](https://agentmods.dev/commands/swarm-ai-research/swarm/merge_session)
Your own site
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/merge_session"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/merge_session/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.

agentmods 80×15 button for merge_session

Your own site · 80×15
<a href="https://agentmods.dev/commands/swarm-ai-research/swarm/merge_session"><img src="https://agentmods.dev/badge/commands/swarm-ai-research/swarm/merge_session.svg" alt="Reviewed on agentmods" width="80" 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 1,231 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01231
Opus 5 $0.00000 $0.00616
Sonnet 5 $0.00000 $0.00246
Haiku 4.5 $0.00000 $0.00123

Measured 9d ago against content hash cb2c6e9c6899, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

merge_session 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 9d 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.

.claude/commands/merge_session.md · 158 lines

How it starts

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

/merge_session

Merge session branch(es) into main via rebase + fast-forward push. Use from inside a session worktree pane to land your work, or with --all to batch merge all sessions from the main repo.

Consolidates the former /merge_all_sessions command (now /merge_session --all).

Usage

/merge_session [--all] [--cleanup]

Examples:

  • /merge_session (merge current session branch into main)
  • /merge_session --all (batch merge all session branches)
  • /merge_session --all --cleanup (merge all + remove worktrees + delete branches)

Argument parsing

Parse $ARGUMENTS to extract:

  • --all: Merge ALL session/pane-* branches sequentially (run from main repo, not a worktree)
  • --cleanup: After merging, remove worktrees and delete branches for successfully merged sessions

Default behavior (single session merge)

1) Verify branch

Run git branch --show-current. If it does not match session/*, print an error and stop:

Error: Not on a session branch (current: <branch>). /merge_session only works from session/* branches.

2) Check working tree

Run git status --porcelain. If there is any output, print an error and stop:

Error: Working tree is dirty. Commit or stash changes before merging.

List the dirty files so the user knows what to deal with.

3) Fetch latest main

git fetch origin main

4) Rebase onto main

git rebase origin/main

If the rebase fails with conflicts:

  • Run git rebase --abort
  • Run git diff --name-only --diff-filter=U to list conflicting files
  • Print the list and stop:
    Rebase conflict — aborted. Conflicting files:
      <file1>
      <file2>
    Resolve manually or coordinate with the other session.
    

5) Push to main

git push origin HEAD:main

If the push is rejected (non-fast-forward):

  • Fetch again: git fetch origin main
  • Rebase again: git rebase origin/main (abort on conflict as above)
  • Retry push once: git push origin HEAD:main
  • If it fails again, report the error and stop.

Read the full file on GitHub · 158 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.

  1. 9d ago First seen · 158 lines · 0 tokens per session scan A cb2c6e9c6899

Subscribe to this mod's changes

merge_session is a command published in the GitHub repository swarm-ai-research/swarm (42 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,231 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.