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/mtnyilmaz/agents/workflow-git-worktreesnpx skills add mtnyilmaz/agents --skill workflow-git-worktreesgit clone --depth 1 https://github.com/mtnyilmaz/agentsWrote 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/mtnyilmaz/agents/workflow-git-worktrees)<a href="https://agentmods.dev/skills/mtnyilmaz/agents/workflow-git-worktrees"><img src="https://agentmods.dev/badge/skills/mtnyilmaz/agents/workflow-git-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.00052 | $0.01907 |
| Opus 5 | $0.00026 | $0.00954 |
| Sonnet 5 | $0.00010 | $0.00381 |
| Haiku 4.5 | $0.00005 | $0.00191 |
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 3d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Overview
Git worktrees give you an isolated working directory on a new branch, sharing the same .git database as the main clone. You can switch branches, run installs, and execute plans without disturbing your main checkout.
Core principle: Systematic directory selection + safety verification + clean baseline = reliable isolation.
When to Use
- Before executing any implementation plan (
workflow-executing-plans,workflow-subagent-driven) - Before a feature branch that needs to coexist with other in-progress work
- Before long-running autonomous sessions (hours of subagent work)
- Before experiments that might leave the tree dirty
When NOT to use:
- Tiny, single-commit fixes where branching in the main checkout is faster
- Read-only investigations (just
git log, no code changes) - Environments where worktrees are disabled (some hosted dev containers)
The Workflow
Pick directory ─→ Verify ignored ─→ Create worktree + branch ─→ Project setup ─→ Test baseline ─→ Report ready
Step 1 — Pick the Worktrees Directory
Priority order — don't ask if a higher-priority option already answers:
1a. Existing directories
ls -d .worktrees 2>/dev/null
ls -d worktrees 2>/dev/null
If either exists, use it. If both exist, .worktrees/ wins.
1b. Repo convention
Check CLAUDE.md / AGENTS.md / .agents/project.json for a worktrees preference:
grep -iE "worktree.*director|worktrees_dir" CLAUDE.md AGENTS.md .agents/project.json 2>/dev/null
If a preference is specified, use it.
1c. Ask the human
If no existing directory and no documented preference:
No worktree directory found. Where should I create worktrees?
1. .worktrees/ (project-local, hidden — preferred)
2. ~/.config/agents/worktrees/<project-name>/ (global, outside project)
Which one?
Step 2 — Verify It's Ignored (Project-Local Only)
If you chose .worktrees/ or worktrees/, it must be in .gitignore or worktree contents will get committed by accident.
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.
- 3d ago First seen · 225 lines · 52 tokens per session scan A 62185573b225
using-git-worktrees is a skill published in the GitHub repository mtnyilmaz/agents (6 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 1,907 once invoked, about $0.0003 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…