using-git-worktrees

A workflow for creating an isolated Git worktree before feature work. A Git worktree is a separate working directory linked to the same repository, so changes can be kept apart from the main checkout.

In plain words
What is it for?
Use it before implementing a feature or running an implementation plan that needs an isolated workspace.
Why use it?
It reduces the risk of mixing feature changes with existing work in the current directory.

Skill for Claude CodeCodex

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 skills/codeanqiang-ma/dsh-superpowers/using-git-worktrees
Any agent
npx skills add codeAnqiang-ma/dsh-superpowers --skill using-git-worktrees
Clone the repo
git clone --depth 1 https://github.com/codeAnqiang-ma/dsh-superpowers

Made for: Claude Code, Codex.

Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,623 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00036 $0.01623
Opus 5 $0.00018 $0.00812
Sonnet 5 $0.00007 $0.00325
Haiku 4.5 $0.00004 $0.00162

Measured 2d ago against content hash 8cfb86f12126, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

using-git-worktrees 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 2d 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.

skills/using-git-worktrees/SKILL.md · 168 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

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. 2d ago First seen · 168 lines · 36 tokens per session scan A 8cfb86f12126

Subscribe to this mod's changes

using-git-worktrees is a skill published in the GitHub repository codeAnqiang-ma/dsh-superpowers (5 stars, last pushed 19d ago), with no licence file. It adds 36 tokens to every session and 1,623 once invoked, about $0.0002 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.