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.
curl -O https://raw.githubusercontent.com/swarm-ai-research/swarm/main/.claude/commands/merge_session.mdgit clone --depth 1 https://github.com/swarm-ai-research/swarmWrote 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/commands/swarm-ai-research/swarm/merge_session)<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.
<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>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.00000 | $0.01231 |
| Opus 5 | $0.00000 | $0.00616 |
| Sonnet 5 | $0.00000 | $0.00246 |
| Haiku 4.5 | $0.00000 | $0.00123 |
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.
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 ALLsession/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=Uto 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.
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.
- 9d ago First seen · 158 lines · 0 tokens per session scan A cb2c6e9c6899
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.
Other commands, from other repositories
eval-merge
Use the Read tool to load .skill-compass/{skill-name}/manifest.json. Verify.
speckit.git.feature
Create a feature branch with sequential or timestamp numbering.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
speckit.git.initialize
Initialize a Git repository with an initial commit.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
speckit.git.remote
Detect Git remote URL for GitHub integration.