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 skills add oleg494/coding-kit --skill using-git-worktreesgit clone --depth 1 https://github.com/oleg494/coding-kitWrote 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/oleg494/coding-kit/using-git-worktrees)<a href="https://agentmods.dev/skills/oleg494/coding-kit/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/using-git-worktrees/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/oleg494/coding-kit/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/oleg494/coding-kit/using-git-worktrees.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00036 | $0.01614 |
| Opus 5.5 | $0.00014 | $0.00646 |
| Sonnet 5.5 | $0.00007 | $0.00323 |
| Haiku 4.5 | $0.00004 | $0.00161 |
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 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.
This is a copy
98% identical to using-git-worktrees — 83 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Overview
Use isolation when the task or concurrent writers require it. For a bounded local change in a usable checkout, work in place unless the user requested otherwise. Do not manufacture a workspace decision before implementation.
Core principle: Preserve existing work. Reuse existing isolation; prefer native tools when creating it, then fall back to git.
Step 0: Detect Existing Isolation
Before creating anything, check if you are already in an isolated workspace.
GIT_DIR=$(cd "$(git rev-parse --git-dir)" 2>/dev/null && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" 2>/dev/null && pwd -P)
BRANCH=$(git branch --show-current)
Submodule guard: GIT_DIR != GIT_COMMON is also true inside git submodules. Before concluding "already in a worktree," verify you are not in a submodule:
# If this returns a path, you're in a submodule, not a worktree — treat as normal repo
git rev-parse --show-superproject-working-tree 2>/dev/null
If GIT_DIR != GIT_COMMON (and not a submodule): You are already in a linked worktree. Skip to Step 2 (Project Setup). Do NOT create another worktree.
Report with branch state:
- On a branch: "Already in isolated workspace at
<path>on branch<name>." - Detached HEAD: preserve the externally managed workspace; name a branch only if authorized integration requires one.
If GIT_DIR == GIT_COMMON (or in a submodule): You are in a normal repo checkout.
Honor the user's declared workspace preference. With no isolation need, work in place and continue to Step 2. If isolation is required, use the platform's existing task-isolation mechanism or a task-scoped worktree; ask only when an unresolved workspace choice would move, discard or interfere with user work.
Step 1: Create Isolated Workspace
You have two mechanisms. Try them in this order.
1a. Native Worktree Tools (preferred)
Isolation is needed or requested (Step 0). Use a native facility such as EnterWorktree, WorktreeCreate, /worktree or --worktree if available, then continue to Step 2.
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 Changed 4db44b119133
- 8d ago Changed 343ed8116383
- 11d ago Changed ce56dac8d5a6
- 25d ago Changed b9dedbb6df46
- 26d ago Changed 7d9163519b11
- 1mo ago Changed 2d6137a81f2b
- 1mo ago Changed · -19 lines 124fa26968dd
- 1mo ago Changed b2d63d784ab1
- 1mo ago Changed 5807af8c677b
- 1mo ago First seen · 174 lines · 36 tokens per session scan A 8efb144b92bd
using-git-worktrees is a skill published in the GitHub repository oleg494/coding-kit (3 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 1,614 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 98% identical to using-git-worktrees, differing in 83 lines, and is treated as a copy.
Other skills, from other repositories
auto-commit
Autonomously group, stage, and commit repository changes into atomic commits.
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
spec-kitty-git-workflow
Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…
resolve-pr-comments
This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
update-pr-summary
This skill should be used when user asks to "update PR summary", "update PR description", "rewrite PR body", "refresh PR title and body", or explicitly invokes "update-pr-summary".
spk-admin-git-workflow
Operate Spec Kitty git workflows, worktrees, safe commits, merge preflights, stale state checks, and recovery.