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/maxedapps/agent-skills/use-worktreesnpx skills add maxedapps/agent-skills --skill use-worktreesgit clone --depth 1 https://github.com/maxedapps/agent-skillsWrote 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.
[](https://agentmods.dev/skills/maxedapps/agent-skills/use-worktrees)<a href="https://agentmods.dev/skills/maxedapps/agent-skills/use-worktrees"><img src="https://agentmods.dev/badge/skills/maxedapps/agent-skills/use-worktrees.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00073 | $0.00777 |
| Opus 5 | $0.00036 | $0.00388 |
| Sonnet 5 | $0.00015 | $0.00155 |
| Haiku 4.5 | $0.00007 | $0.00078 |
Grade A, and why
use-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 4d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Use git worktrees
Location
All worktrees live in ~/worktrees/<project>/<worktree>, where <project> is the repo's directory name and <worktree> matches the branch name:
git worktree add ~/worktrees/course-platform/milestone-4-auth -b milestone-4-auth <target-branch>
Never create worktrees inside the repository or scattered elsewhere. git worktree list shows what exists.
Setup after creating
- Follow the repository's setup instructions and install dependencies in the worktree; generated or ignored dependency directories are not shared between checkouts.
- Give deployments from concurrent worktrees a dedicated stage/environment. Never let parallel checkouts mutate the same deployment state.
- For delegated work, also follow
use-subagents; the parent agent owns all worktree creation, integration, and cleanup.
Working in the worktree
- All work for the feature happens on the worktree's branch, committed incrementally. The main checkout stays untouched and free for parallel work.
- Sync direction during work is always target branch → worktree branch (
git merge <target-branch>inside the worktree) at natural checkpoints, and mandatorily before touching anything that parallel work may have changed. Never rebase or rewrite shared branches. - After every sync, run the repository's full check suite.
- Sync conflict rules:
- Sequential migrations: if the target branch took a number this branch also uses, renumber this branch's migration to the next free slot. Check this on every sync even without a textual conflict.
- Lockfile conflicts: preserve both sides' manifest/workspace changes, then regenerate with the repository's package manager. Never hand-edit a generated lockfile.
- Resolve everything else by reading both sides; the combined test suites are the arbiter.
Merging back
Never merge a worktree branch back into master (or any target branch) automatically. Review cycles happen in the worktree first; the merge happens only when the user explicitly asks for it. When they do:
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.
- 4d ago First seen · 64 lines · 73 tokens per session scan A c1d66d550f8c
use-worktrees is a skill published in the GitHub repository maxedapps/agent-skills (58 stars, last pushed 19d ago), licensed MIT. It adds 73 tokens to every session and 777 once invoked, about $0.0004 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-30.
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…