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/ourines/worktree-task-plugin/mergegit clone --depth 1 https://github.com/ourines/worktree-task-pluginWhat 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.00007 | $0.00251 |
| Opus 5 | $0.00003 | $0.00125 |
| Sonnet 5 | $0.00001 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
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.
What it actually says
Merge Feature Branch
Merge a completed feature branch into the current branch using worktree + tmux with automatic conflict resolution.
Usage
Provide the feature branch name to merge into the current branch.
Example
User on dev branch: "Merge feature-auth into dev"
User on main branch: "Merge feature/new-api into main"
Execution
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/merge.py "<feature-branch>"
Prerequisites
- Must be on the target branch (e.g., dev, main)
- Feature branch must exist
- tmux must be installed
What Happens
- Checks if feature branch has a worktree
- If worktree exists:
- Enters the worktree
- Rebases feature branch onto current branch
- Resolves any conflicts
- Returns to main repo
- Merges feature branch into current branch
- Resolves any merge conflicts using Claude Code in tmux
After Launch
Use tmux attach -t merge-<feature>-to-<target> to monitor progress.
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 · 45 lines · 7 tokens per session scan A 7289678aa6fa
merge is a command published in the GitHub repository ourines/worktree-task-plugin (39 stars, last pushed 8mo ago), licensed MIT. It adds 7 tokens to every session and 251 once invoked, about $0.0000 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
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.