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.
git clone --depth 1 https://github.com/axiomantic/spellbookWrote 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/axiomantic/spellbook/merge-worktree-execute)<a href="https://agentmods.dev/commands/axiomantic/spellbook/merge-worktree-execute"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/merge-worktree-execute/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/axiomantic/spellbook/merge-worktree-execute"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/merge-worktree-execute.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.00020 | $0.00310 |
| Opus 5.5 | $0.00008 | $0.00124 |
| Sonnet 5.5 | $0.00004 | $0.00062 |
| Haiku 4.5 | $0.00002 | $0.00031 |
Grade A, and why
merge-worktree-execute 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 1mo 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.
What it actually says
Phase 2: Sequential Round Merging
Invariant Principles
- Dependency order is non-negotiable - Merging out of dependency order produces phantom conflicts and broken intermediate states
- Test after every round - Each round must pass the full test suite before the next round begins; never batch merges without verification
- Conflicts escalate to resolution phase - Merge conflicts are not resolved inline; they invoke the dedicated conflict resolution workflow
For each round, merge worktrees in dependency order:
# Checkout and update base
cd [main-repo-path]
git checkout [base-branch]
git pull origin [base-branch]
# Merge each worktree in round
WORKTREE_BRANCH=$(cd [worktree-path] && git branch --show-current)
git merge $WORKTREE_BRANCH --no-edit
If merge succeeds: Log success, continue to next worktree.
If conflicts: Proceed to Phase 3 (invoke /merge-worktree-resolve), then continue with remaining worktrees.
Run tests after EACH round:
pytest # or npm test, cargo test, etc.
If tests fail:
- Invoke
systematic-debuggingskill - Fix issues, commit fixes
- Re-run tests until passing
- Do NOT proceed to next round until green
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.
- 1mo ago First seen · 40 lines · 20 tokens per session scan A 9e604dd54602
merge-worktree-execute is a command published in the GitHub repository axiomantic/spellbook (10 stars, last pushed 3d ago), licensed MIT. It adds 20 tokens to every session and 310 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
worktree
Create a git worktree for isolated feature/fix work.
test-suite
Run comprehensive test suite with coverage analysis.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
pr-ready
Run the project's pre-commit review loop to determine whether the current branch is ready to push — lint, tests, parallel pr-review-toolkit agents plus an over-engineering audit, fix-and-re-run until convergence.
clean_gone
Cleans up all git branches marked as [gone] (branches that have been deleted on the remote but still exist locally), including removing associated worktrees.
autotask
Execute development task autonomously from description to PR-ready - handles implementation, testing, and git workflow without supervision.