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/wazimmerman/zimster/using-git-worktreesnpx skills add wazimmerman/zimster --skill using-git-worktreesgit clone --depth 1 https://github.com/wazimmerman/zimsterWrote 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/wazimmerman/zimster/using-git-worktrees)<a href="https://agentmods.dev/skills/wazimmerman/zimster/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/wazimmerman/zimster/using-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.00020 | $0.00460 |
| Opus 5 | $0.00010 | $0.00230 |
| Sonnet 5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Use isolation for consequential implementation, parallel work, or experiments. A clean dedicated feature branch can be sufficient; a worktree is not ritual.
Detect first
Run read-only commands:
git rev-parse --show-toplevel
git rev-parse --git-dir
git rev-parse --git-common-dir
git branch --show-current
git status --short
git worktree list --porcelain
Interpretation:
- different git-dir/common-dir: already linked worktree;
- empty branch: detached HEAD; understand harness controls;
- dirty tree: preserve unrelated changes;
- clean dedicated feature branch: usually isolated enough.
Deterministic policy
| Context | Behavior |
|---|---|
| Disposable/test repo explicitly intended for direct work | Default branch allowed; do not commit unless policy/request says so. |
| Existing project on default branch | Stop before implementation or create a feature branch/worktree unless explicitly authorized. |
| Existing clean feature branch/worktree | Continue there and commit at verified slice boundaries. |
| Dirty checkout with unrelated changes | Create a separate worktree/branch; do not move or overwrite changes. |
| Parallel implementers | Give each an isolated branch/worktree or strictly disjoint ownership; never share one index concurrently. |
| User says do not commit | Isolation may still be used, but leave changes uncommitted and report them. |
Location and creation
Respect repository instructions and existing .worktrees/worktrees
conventions. Otherwise use a project-local ignored directory that works on the
host OS. Avoid hard-coded home paths and shell assumptions. Confirm the
location is ignored before creation.
After creation, confirm branch/root, install only required dependencies, run the smallest baseline, and record path/branch/commit policy in the Git-local Zimster run record when durable state is required.
Cleanup
Remove a worktree only after branch outcome is decided and evidence is preserved. Never delete uncommitted work. Harness-managed worktrees may require native handoff controls; report this rather than forcing Git operations.
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 · 59 lines · 20 tokens per session scan A 62dd7380dcbb
using-git-worktrees is a skill published in the GitHub repository wazimmerman/zimster (2 stars, last pushed 15d ago), licensed MIT. It adds 20 tokens to every session and 460 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
treework-manual
Use TreeWork Manual when the user asks for it, or when the Agent judges that organizing ongoing, multi-part work as a persistent Markdown Tree would improve direction, continuity, recovery, or handoff. Adapt the Tree's depth and document detail to the user's needs, domain, and situation rather than a fixed threshold.
treework
Use TreeWork, a tree-guided development plugin for complex or evolving software projects that need staged alignment, pre-coding technical Specs, declarative project-tree planning, branch-scoped Git worktrees, durable recovery, and protected completion. It teaches the Agent to move through development along the Tree…
repository-bootstrap
Audit and establish or upgrade the canonical repository governance baseline. Use only when explicitly asked to bootstrap, standardize, or upgrade a repository; do not use for feature development or source-code restructuring.
repository-hygiene
Perform a read-only evidence-based audit of stale docs, agent files, scripts, generated artifacts, duplicate code, and optional tools. Use only when explicitly asked for cleanup or governance review; do not delete or refactor during the audit.
safe-change
Trace, implement, test, and independently review one bounded software change. Use for ordinary feature, bug-fix, or refactor work after the repository is bootstrapped; do not use for broad repository cleanup, production operations, or undefined rewrites.
apex-workflow
Use for configurable, high-rigor app execution across repos. Selects the lightest safe workflow mode from an app profile, creates or uses a slice manifest, and routes product, tracker, code-intelligence, UI/UX, and verification gates without hard-coding one app's rules.