sup-using-git-worktrees

A Git workflow for creating separate worktrees, which are additional working folders connected to the same repository. It chooses suitable folder locations and checks that the setup is safe before feature work begins.

In plain words
What is it for?
Use it before starting feature work or carrying out an implementation plan. It helps create and verify an isolated Git workspace.
Why use it?
It keeps feature changes isolated from the current working folder. This reduces the chance that unfinished work or unrelated edits interfere with the feature.

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

Made for: Claude Code, Codex.

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,346 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.00037 $0.01346
Opus 5 $0.00018 $0.00673
Sonnet 5 $0.00007 $0.00269
Haiku 4.5 $0.00004 $0.00135

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

Security

Grade A, and why

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

.claude/skills/using-git-worktrees/SKILL.md · 219 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

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 · 219 lines · 37 tokens per session scan A 27622029cf2b

Subscribe to this mod's changes

sup-using-git-worktrees is a skill published in the GitHub repository rahulcvwebsitehosting/wayfinder (2 stars, last pushed 2mo ago), licensed AGPL-3.0. It adds 37 tokens to every session and 1,346 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.