What is flow-next-worktree-kit?

A toolkit for managing Git worktrees, which are separate working folders connected to one repository. It also copies environment files such as .env files into a worktree.

Use it to create, list, switch between, and clean up worktrees, or copy environment files into one.

It keeps parallel feature work and reviews separated, reducing branch and workspace mix-ups.

flow-next-worktree-kit — Skill for Claude Code and Codex by gmickel

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.

Any agent

npx skills add gmickel/flow-next --skill flow-next-worktree-kit

Clone the repo

git clone --depth 1 https://github.com/gmickel/flow-next

Made for: Claude Code, Codex.

Or install flow-next, the plugin that ships this one along with the rest of its 29 skills, 26 commands, 21 agents.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-worktree-kit/github.svg)](https://agentmods.dev/skills/gmickel/flow-next/flow-next-worktree-kit)

Your own site

<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-worktree-kit"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-worktree-kit/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/gmickel/flow-next/flow-next-worktree-kit"><img src="https://agentmods.dev/badge/skills/gmickel/flow-next/flow-next-worktree-kit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 595 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. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

high Privilege Escalation · line 3
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.

Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.

How audits are shown

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.

Model	Per session	Once invoked
Fable 5.1	$0.00043	$0.00595
Opus 5.5	$0.00017	$0.00238
Sonnet 5.5	$0.00009	$0.00119
Haiku 4.5	$0.00004	$0.00060

Measured 24d ago against content hash 25644306a389, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

flow-next-worktree-kit 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 24d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/worktree.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/flow-next/codex/skills/flow-next-worktree-kit/SKILL.md · 39 lines

What it actually says

Worktree kit

Use the manager script for all worktree actions.

WORKTREE_SH="${CODEX_HOME:-$HOME/.codex}/scripts/worktree.sh"
[ -f "$WORKTREE_SH" ] || WORKTREE_SH="<plugin-root>/skills/flow-next-worktree-kit/scripts/worktree.sh"   # <plugin-root> = the directory two levels above this skill's SKILL.md file (the harness gave you that file's absolute path when the skill loaded); substitute it literally
bash "$WORKTREE_SH" <command> [args]

Commands:

create <name> [base]
list
switch <name> (prints the worktree path; it cannot change your shell's directory - use cd "$(... switch <name>)")
cleanup [<name>...] [--yes] (no args = interactive; names skip the prompt; --yes skips the confirmation, required off a terminal)
copy-env <name>

Safety notes:

create does not change the current branch
create sets no upstream on the new branch (--no-track) - under the upstream-based push modes (simple, upstream, current) a bare git push cannot aim at the base branch; under the default push.default=simple (without push.autoSetupRemote) the first push needs git push -u origin <name> (legacy push.default=matching pushes all name-matched branches regardless of upstream)
cleanup does not force-remove worktrees and does not delete branches
cleanup deletes the worktree directory (including ignored files); removal fails if the worktree is not clean
.env* is copied with no overwrite (symlinks skipped)
refuses to operate if .worktrees/ or any worktree path component is a symlink
copy-env only targets registered worktrees
origin fetch is optional; local base refs are allowed
fetch from origin only when base looks like a branch
Worktrees live under .worktrees/
create initializes .worktrees/.gitignore (* plus !.gitignore) when absent, so git add -A cannot stage nested worktrees as gitlinks; existing custom ignore files are preserved

Shared claim state. Parallel agents in sibling worktrees driving flowctl on the same repo share claim state via .git/flow-state. Set FLOW_STATE_DIR per agent (outside the tree) when running flow pipelines concurrently.

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

24d ago Changed · +2 lines 25644306a389
1mo ago First seen · 37 lines · 43 tokens per session scan A 683827af1f9e

Subscribe to this mod's changes

flow-next-worktree-kit is a skill published in the GitHub repository gmickel/flow-next (712 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 595 once invoked, about $0.0002 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-08-30.

Claude Code Code review Git and workflow Planning Writing and docs execution marketplace plugin workflow

pr

Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.

umputun/cc-thingz · 51 tokens

backlog

Read, work, and maintain a Git repo's deferred-work items in docs/backlog/, one file per item. Use when the user says "backlog", "check backlog", "what's on my backlog", "work the backlog", "address the backlog", "add to backlog", "clean up backlog", or when a review or task produced items that are real but not being…

umputun/cc-thingz · 96 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens

last-tag

Show commits since the last tag in a formatted table. Use when user asks "what changed since last release", "commits since last tag", "last-tag", "what's new", or wants to see recent unreleased changes.

umputun/cc-thingz · 50 tokens

plugin-code-review-orchestrated

Orchestrates a code review of the spring-plugin repository through scope/context passes, routing, domain reviewer subskills, and per-artifact validation. Use when asked to review a PR, diff, commit, branch, module, or file set, to run a full orchestrated review, or to produce a validated review report.

explyt/spring-plugin · 72 tokens

review-scope-resolver

Normalizes a PR, diff, commit, branch, file list, directory, module, class, or function into an exact review target with semantic clusters and routing signals for domain reviewer subskills. Use as the first pass of an orchestrated code review, when asked to resolve review scope, or when a raw review reference must be…

explyt/spring-plugin · 83 tokens