Agent-Workflow-Kit: Command for Claude Code

.claude/commands/apply-worktree.md

apply-worktree is a command for Claude Code from Bita71/Agent-Workflow-Kit. It costs 0 tokens per session (102 once invoked), scanned A, original, MIT.

A command that transfers changes from a separate Git worktree into the main checkout when explicitly requested.

In plain words
What is it for?
Applying a worktree's tracked changes and copied untracked files to the base checkout, then deciding whether to remove the worktree.
Why use it?
It avoids manually moving tracked and untracked files between worktrees while leaving the result unstaged for review.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is Bita71/Agent-Workflow-Kit's own configuration. It tells Claude Code how to work on Agent-Workflow-Kit itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Agent-Workflow-Kit configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Bita71/Agent-Workflow-Kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Bita71/Agent-Workflow-Kit/master/.claude/commands/apply-worktree.md
Clone the repo
git clone --depth 1 https://github.com/Bita71/Agent-Workflow-Kit

Made for: Claude Code.

Wrote 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.

agentmods badge for apply-worktree

README.md
[![agentmods](https://agentmods.dev/badge/commands/bita71/agent-workflow-kit/apply-worktree/github.svg)](https://agentmods.dev/commands/bita71/agent-workflow-kit/apply-worktree)
Your own site
<a href="https://agentmods.dev/commands/bita71/agent-workflow-kit/apply-worktree"><img src="https://agentmods.dev/badge/commands/bita71/agent-workflow-kit/apply-worktree/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.

agentmods 80×15 button for apply-worktree

Your own site · 80×15
<a href="https://agentmods.dev/commands/bita71/agent-workflow-kit/apply-worktree"><img src="https://agentmods.dev/badge/commands/bita71/agent-workflow-kit/apply-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 102 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original 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.1 $0.00000 $0.00102
Opus 5.5 $0.00000 $0.00041
Sonnet 5.5 $0.00000 $0.00020
Haiku 4.5 $0.00000 $0.00010

Measured 2mo ago against content hash 80579b8d7dda, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

apply-worktree 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 2mo 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.

.claude/commands/apply-worktree.md · 10 lines

What it actually says

apply-worktree

Apply a worktree's diff into the base checkout — only when the user explicitly asks to transfer changes.

Follow the Apply section of docs/ai/recipes/git-worktree.md exactly. Transfer tracked changes via a temporary commit + cherry-pick --no-commit and untracked files by copy; leave the result unstaged in the base checkout for the user to review and commit. After apply, ask whether to delete the worktree.

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. 2mo ago First seen · 10 lines · 0 tokens per session scan A 80579b8d7dda

Subscribe to this mod's changes

apply-worktree is a command published in the GitHub repository Bita71/Agent-Workflow-Kit (1 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 102 tokens. 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-31.