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/wrannaman/agentic-engineering/worktreenpx skills add wrannaman/agentic-engineering --skill worktreegit clone --depth 1 https://github.com/wrannaman/agentic-engineeringWhat 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.00012 | $0.02052 |
| Opus 5 | $0.00006 | $0.01026 |
| Sonnet 5 | $0.00002 | $0.00410 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
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 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Management
List and create git worktrees using gtr (git-worktree-runner). Complements /git-cleanup to provide full worktree lifecycle: create → list/manage → cleanup.
When to Use
- Starting a new workstream and want branch isolation, then continuing work in the same session
- Creating a worktree and immediately executing a plan there (most common)
- Working on multiple features in parallel
- Checking what worktrees exist and their PR status
- Creating a worktree mid-session after realizing you need isolation
Arguments
| Argument | Default | Description |
|---|---|---|
list |
(default) | List all worktrees with PR status and last commit |
create <branch> |
— | Create a new worktree for the given branch |
create <branch> --from-current |
— | Create a worktree branching from the current branch |
Process
Command: list (default, no arguments)
-
Get worktree list:
git gtr list -
Enrich each worktree with PR status and last commit:
# For each branch in the worktree list: gh pr list --head <branch> --state open --json number,title,url --limit 1 git log -1 --format='%h %s (%cr)' <branch> -
Display as a table:
## Worktrees | Path | Branch | PR | Last Commit | |------|--------|----|-------------| | ~/projects/myapp | main | — | abc1234 fix typo (2 hours ago) | | ~/projects/myapp-feat-auth | feat/auth | #42 Add OAuth | def5678 add token refresh (1 day ago) | | ~/projects/myapp-fix-bug | fix/login-bug | — | ghi9012 debug login (3 days ago) |
Command: create <branch-name>
-
If no branch name provided, ask for one using AskUserQuestion.
-
Preflight: ensure worktrees are stored inside the repo. Worktrees MUST be inside the repo so they stay within Claude Code's sandbox. Check and fix before creating:
git gtr config get gtr.worktrees.dir- If it returns
.worktrees→ proceed to step 3. - If it returns anything else or is empty → configure it:
Tell the user: "Configured this repo to store worktrees in# Add [worktrees] dir = .worktrees to .gtrconfig (create if missing) # If .gtrconfig doesn't exist: printf '[worktrees]\n dir = .worktrees\n' > .gtrconfig # If .gtrconfig exists but has no [worktrees] section: # prepend the section before existing content # Ensure .worktrees/ is in .gitignore grep -qxF '/.worktrees/' .gitignore 2>/dev/null || echo '/.worktrees/' >> .gitignore.worktrees/(inside the repo) so Claude Code can access them without permission prompts."
- If it returns
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 · 223 lines · 12 tokens per session scan A bbde06ade22f
worktree is a skill published in the GitHub repository wrannaman/agentic-engineering (2 stars, last pushed 4mo ago), licensed MIT. It adds 12 tokens to every session and 2,052 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.