plan-worktree-create

A command that creates a separate Git worktree and feature branch for new work. A worktree is an additional folder linked to the same repository.

In plain words
What is it for?
Starting feature development from the current branch or from a specified base branch.
Why use it?
It keeps feature changes isolated while allowing another branch or working directory to remain available.

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/xonovex/platform/plan-worktree-create
Clone the repo
git clone --depth 1 https://github.com/xonovex/platform
Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 186 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00010 $0.00186
Opus 5 $0.00005 $0.00093
Sonnet 5 $0.00002 $0.00037
Haiku 4.5 $0.00001 $0.00019

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

Security

Grade A, and why

plan-worktree-create 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.

packages/command/command-workflow/commands/plan-worktree-create.md · 25 lines

What it actually says

/xonovex-workflow:plan-worktree-create - Create Feature Worktree

Arguments

/plan-worktree-create [feature-name] [--from <branch>]

  • feature-name: Name of the feature (required) - used in directory and branch names
  • --from <branch>: Create feature from specific branch instead of current branch

Delegation

Load the git-guide skill (plugin xonovex-skill-git) and perform its worktree-create operation with these arguments. The skill is the source of truth for the procedure, output format, and gotchas. Do not restate them.

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 · 25 lines · 10 tokens per session scan A 53dcbaa5551a

Subscribe to this mod's changes

plan-worktree-create is a command published in the GitHub repository xonovex/platform (5 stars, last pushed 2d ago), licensed MIT. It adds 10 tokens to every session and 186 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-08-31.