power-worktree

power-worktree is a skill for Claude Code, Codex from pwdev-solucoes/pwdev-claude-marketplace. It costs 23 tokens per session (575 once invoked), scanned A, original, Apache-2.0.

A coding workflow guide for creating a separate Git worktree, which is an isolated copy of a repository for feature work.

In plain words
What is it for?
Use it when starting a feature or following an implementation plan that needs its own workspace.
Why use it?
It helps keep unfinished changes separate from the current workspace and reduces the risk of mixing files or disrupting other work.

Skill for Claude CodeCodex

Written for Claude Code and Codex: shipped in a Claude Code plugin, but also agents/openai.yaml present.

Part of the pwdev-power plugin — 15 skills, 3 agents shipped together

Good fit Use it when starting a feature or following an implementation plan that needs its own workspace.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pwdev-solucoes/pwdev-claude-marketplace/power-worktree
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 pwdev-solucoes/pwdev-claude-marketplace --skill power-worktree
Clone the repo
git clone --depth 1 https://github.com/pwdev-solucoes/pwdev-claude-marketplace

Made for: Claude Code, Codex.

Or install pwdev-power, the plugin that ships this one along with the rest of its 15 skills, 3 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.

agentmods badge for power-worktree

README.md
[![agentmods](https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-worktree/github.svg)](https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-worktree)
Your own site
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-worktree"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-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 power-worktree

Your own site · 80×15
<a href="https://agentmods.dev/skills/pwdev-solucoes/pwdev-claude-marketplace/power-worktree"><img src="https://agentmods.dev/badge/skills/pwdev-solucoes/pwdev-claude-marketplace/power-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 575 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.00023 $0.00575
Opus 5 $0.00012 $0.00287
Sonnet 5 $0.00005 $0.00115
Haiku 4.5 $0.00002 $0.00057

Measured 6d ago against content hash 4227c3759fe9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

power-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 6d 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.

plugins/pwdev-power/skills/power-worktree/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Work in an Isolated Workspace

Step 0 — You may already be isolated

Check before creating anything:

GIT_DIR=$(cd "$(git rev-parse --git-dir)" && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" && pwd -P)
git rev-parse --show-superproject-working-tree

If GIT_DIR differs from GIT_COMMON and the third command prints nothing (you are not in a submodule, where the same difference appears for an unrelated reason), you are already in a worktree. Skip to Step 2.

Step 1a — Native tooling first

If your harness has its own worktree mechanism — an EnterWorktree tool, a /worktree command, a --worktree flag — use it.

Running git worktree add when a native tool exists is the most common mistake here: it creates a worktree the harness does not know about, so its own bookkeeping points at the old one, and everything after that is confusing in a way that is hard to trace back.

Step 1b — Fallback

Only if there is no native tool. Get consent first: this changes where the human's work happens.

Choose the location by priority: what the human specified, then an existing .worktrees/, then an existing worktrees/, then .worktrees/ as the default.

Check it is ignored before creating it:

git check-ignore -q .worktrees/ || echo "not ignored — add it to .gitignore first"
git worktree add .worktrees/<slug> -b <branch>

An un-ignored worktree directory turns the entire checkout into untracked noise inside the parent repository.

If git worktree add fails on permissions, you are probably in a sandbox that cannot write where you asked. Say so; do not retry with sudo or a path outside the repository.

Step 2 — Set it up

Install dependencies with the project's real command, read from its manifest. Copy the local environment files the project needs — except anything holding a secret, which the human provides.

Step 3 — Green baseline

Run the test suite before changing anything.

A baseline you did not take is a baseline you will invent later, and the first failure will look like yours whether it is or not. If the suite is already red, say so now and agree what "green" means for this work.

Read the full file on GitHub · 65 lines

Files

What ships with it

1 file 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.

  1. 6d ago First seen · 65 lines · 23 tokens per session scan A 4227c3759fe9

Subscribe to this mod's changes

power-worktree is a skill published in the GitHub repository pwdev-solucoes/pwdev-claude-marketplace (2 stars, last pushed 3d ago), licensed Apache-2.0. It adds 23 tokens to every session and 575 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-09-03.

Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

comet-github

A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.

rpamis/comet · 72 tokens

github-skill

Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.

zeenie-ai/OpenCompany · 51 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

nvca-chart-release

Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.

NVIDIA/nvcf · 61 tokens