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-resolve)<a href="https://agentmods.dev/commands/axiomantic/spellbook/merge-worktree-resolve"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/merge-worktree-resolve/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-resolve"><img src="https://agentmods.dev/badge/commands/axiomantic/spellbook/merge-worktree-resolve.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.00018 | $0.00276 |
| Opus 5.5 | $0.00007 | $0.00110 |
| Sonnet 5.5 | $0.00004 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
merge-worktree-resolve 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 3: Conflict Resolution
Invariant Principles
- Synthesize both sides, never pick one - Conflict resolution must integrate both changesets; either/or resolution loses work
- Interface contracts are the arbiter - When both sides claim different behavior, the implementation plan's interface contract is ground truth
- Verify contracts after every resolution - Type signatures and function behavior must match the contract spec before continuing
When merge conflicts occur, delegate to resolving-merge-conflicts skill with interface contract context.
Invoke resolving-merge-conflicts with:
- Interface contracts (from implementation plan)
- Worktree purpose (what this worktree implemented)
- Expected interfaces (type signatures, function contracts)
After resolution - Contract Verification:
| Check | Action if Failed |
|---|---|
| Type signatures match contract | Fix to match contract spec |
| Function behavior matches spec | Revert to contract-compliant version |
| Both sides honor interfaces | Synthesis is valid |
Violation = fix before git merge --continue
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 · 36 lines · 18 tokens per session scan A 8ed240638a69
merge-worktree-resolve is a command published in the GitHub repository axiomantic/spellbook (11 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 276 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
make-pr
Push the current branch when needed and create a GitHub pull request from the local draft.
draft-pr
Draft a pull request title and body to a local file — no push, no GitHub PR.
gh-review-check
Check unresolved PR review comments and summarize findings.
gh-review-fix-loop
Fix and resolve GitHub PR review threads.
mr-description-creator
Generate and apply MR/PR description directly via gh or glab CLI (project).
worktree
Create a git worktree for isolated feature/fix work.