finish-worktree

A command that merges a completed feature branch from a worktree, which is a separate working directory linked to the same Git repository.

In plain words
What is it for?
It is used to merge completed feature work from a worktree while maintaining linear Git history.
Why use it?
It helps bring finished work into the main history while keeping commits in a straight line.

Command

Install

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.

agentmods
npx agentmods add commands/boneskull/claude-plugins/finish-worktree
Clone the repo
git clone --depth 1 https://github.com/boneskull/claude-plugins
Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,152 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.04152
Opus 5 $0.00006 $0.02076
Sonnet 5 $0.00003 $0.00830
Haiku 4.5 $0.00001 $0.00415

Measured yesterday against content hash d8896b6e8444, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

finish-worktree scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

3. Force-delete the worktree (rm -rf) - files will be lost
plugins/tools/commands/finish-worktree.md · 574 lines

The source is not reproduced here

Licensed BlueOak-1.0.0

The repository is licensed BlueOak-1.0.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

Changes

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.

  1. yesterday First seen · 574 lines · 13 tokens per session scan C d8896b6e8444

Subscribe to this mod's changes

finish-worktree is a command published in the GitHub repository boneskull/claude-plugins (2 stars, last pushed 4d ago), licensed BlueOak-1.0.0. It adds 13 tokens to every session and 4,152 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.