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.
npx agentmods add commands/raine/workmux/mergegit clone --depth 1 https://github.com/raine/workmuxWhat 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 | $0.00015 | $0.01089 |
| Opus 5 | $0.00008 | $0.00544 |
| Sonnet 5 | $0.00003 | $0.00218 |
| Haiku 4.5 | $0.00002 | $0.00109 |
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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merges a branch into a target branch (main by default) and automatically cleans up all associated resources (worktree, tmux window, and local branch).
workmux merge [branch-name] [flags]
:::tip[When to use merge vs remove]
workmux merge performs the git merge locally. Use it when you want to merge directly without a pull request.
If your workflow uses pull requests, the merge happens on the remote after review. In that case, use workmux remove to clean up the worktree after your PR is merged.
:::
Arguments
[branch-name]: Optional name of the branch to merge. If omitted, automatically detects the current branch from the worktree you're in.
Options
| Flag | Description |
|---|---|
--into <branch> |
Merge into the specified branch instead of main. Useful for stacked PRs, git-flow workflows, or merging subtasks into a parent feature branch. If the target branch has its own worktree, the merge happens there; otherwise, the main worktree is used. |
--ignore-uncommitted |
Commit any staged changes before merging without opening an editor. |
--keep, -k |
Keep the worktree, window, and branch after merging (skip cleanup). Useful when you want to verify the merge before cleaning up. |
--cleanup |
Clean up after merging, overriding merge_keep: true. |
--notification |
Show a system notification on successful merge. Useful when delegating merge to an AI agent and you want to be notified when it completes. |
--rebase |
Rebase the feature branch onto the target before merging (creates a linear history via fast-forward merge). If conflicts occur, you'll need to resolve them manually and run git rebase --continue. |
--squash |
Squash all commits from the feature branch into a single commit on the target. You'll be prompted to provide a commit message in your editor. |
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.
- 2d ago First seen · 95 lines · 15 tokens per session scan A 4517895c8495
merge is a command published in the GitHub repository raine/workmux (2,351 stars, last pushed today), licensed MIT. It adds 15 tokens to every session and 1,089 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.