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/axiomantic/spellbook/merge-worktree-executegit 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.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.00310 |
| Opus 5 | $0.00010 | $0.00155 |
| Sonnet 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 yesterday.
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.
- yesterday 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 yesterday), licensed MIT. It adds 20 tokens to every session and 310 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-09-03.
Other commands, from other repositories
generate-tests
This command was migrated to a skill in Claude Code 2.1.3. See: examples/skills/generate-tests/SKILL.md.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
worktree
Create a git worktree for isolated feature/fix work.