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.
npx agentmods add skills/jtsternberg/claude-plugins/create-git-treenpx skills add jtsternberg/claude-plugins --skill create-git-treegit clone --depth 1 https://github.com/jtsternberg/claude-pluginsWhat 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 | $0.00021 | $0.00642 |
| Opus 5 | $0.00010 | $0.00321 |
| Sonnet 5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
create-git-tree 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Tree
Create git worktrees in parallel directories with automatic symlinks to vendor, node_modules, and .env.
Quick Reference
# Resolve this once. Codex: this path resolves under Claude Code; substitute the absolute
# path to this git-tree plugin root, which contains this skill's parent skills/ directory.
GIT_TREE_ROOT="${CLAUDE_PLUGIN_ROOT}"
"$GIT_TREE_ROOT/scripts/git-tree.sh" <branch-name> [--repo <path>] [--create]
Workflow
Run the resolved script with the branch name. If no branch is provided, ask the user.
Flags:
--repo <path>: Target repository (defaults to cwd)--create: Create branch if it doesn't exist
Success output:
Worktree created successfully
Created N symlink(s)
Worktree location: /path/to/gittree-branch
Failure: Script exits non-zero with error message. Common errors:
- "Branch does not exist" → add
--createflag or create branch first - "Worktree directory already exists" → remove existing worktree
- "Branch is already checked out" → use different branch or remove other worktree
What Gets Created
parent/
├── repo/ # Original (real deps)
└── gittree-branch/ # Worktree (symlinked deps)
Managing Worktrees
# List all worktrees
git worktree list
# Remove a worktree
git worktree remove gittree-branch-name
When NOT to Use
- Different dependency versions needed → Remove symlinks and install:
rm vendor && composer install - Temporary one-file changes → Use
git stash - Branch already checked out → Remove existing worktree first:
git worktree remove <path>
Web Server Integration
Need to serve a worktree via local web server (LocalWP, nginx, etc)?
See WEBSERVER-WORKTREES.md for swap/restore scripts that temporarily redirect your web server's document root.
Troubleshooting
Errors or unexpected behavior? → See TROUBLESHOOTING.md
Common issues covered: broken symlinks, pre-commit hook failures, containerized environments.
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.
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.
- 2d ago First seen · 86 lines · 21 tokens per session scan A 6ab6bb42b8e5
create-git-tree is a skill published in the GitHub repository jtsternberg/claude-plugins (5 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 642 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…