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 byerlikaya/claude-starter-kit --skill worktreegit clone --depth 1 https://github.com/byerlikaya/claude-starter-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/byerlikaya/claude-starter-kit/worktree)<a href="https://agentmods.dev/skills/byerlikaya/claude-starter-kit/worktree"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/worktree/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/byerlikaya/claude-starter-kit/worktree"><img src="https://agentmods.dev/badge/skills/byerlikaya/claude-starter-kit/worktree.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.00056 | $0.00813 |
| Opus 5.5 | $0.00022 | $0.00325 |
| Sonnet 5.5 | $0.00011 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Isolation
Trigger phrases: "worktree", "git worktree", "isolate the changes", "sandbox this work", "parallel file edits"
One rule: never let risky or parallel work run on top of uncommitted changes in the shared tree. A git worktree gives a second working copy of the same repo on its own branch — you experiment or fan out agents there, and the main tree (with your in-progress edits) is physically untouched. Throw the worktree away and nothing you cared about is lost.
Kit adaptation (local, .claude/): this exists because verification/fan-out subagents have discarded a session's uncommitted work by running a destructive git command over the shared tree. Those commands (
reset --hard,clean -f,checkout -- .,restore) are §4.5-gated — but the real fix is to not put them near unsaved work. The Agent tool'sisolation: "worktree"does this automatically for parallel mutating agents; reach for it there.
When to isolate
- Fan-out that writes files — two+ agents editing the same repo in parallel would collide; give each its own worktree.
- A throwaway experiment — you might keep it or bin it; a worktree makes "bin it" a one-liner, not a
reset --hard. - A dirty tree you can't commit yet — you have unsaved work but need to try something risky; isolate rather than stash-and-pray.
- Skip it for a single, in-place edit on a clean tree — a worktree is overhead there.
How
- Detect — are you already in a worktree?
[ "$(git rev-parse --git-dir)" != "$(git rev-parse --git-common-dir)" ]is true inside one; don't nest. - Create —
git worktree add ../wt-<name> -b <branch>(new branch) orgit worktree add ../wt-<name> <existing>. It shares the object store, so it's cheap. - Work there — cd into it; edits, builds, and agent runs stay local to that copy.
- Fold back or discard — keep: commit on its branch, then merge. Discard:
git worktree remove ../wt-<name>(add--forceonly if you mean to drop its changes). - Clean up —
git worktree pruneremoves stale entries. Never leave orphaned worktrees around.
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.
- 1mo ago First seen · 43 lines · 56 tokens per session scan A c03a44fb8264
worktree is a skill published in the GitHub repository byerlikaya/claude-starter-kit (24 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 813 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
fork-fleet
Fork divergence monitor - tracks where the fleet's active forks diverge in CODE (unique commits, new/modified skills) and CONFIG (enable/var/model/schedule vs upstream), gated on real change.
pr-review
Review open PRs two ways - default is a per-PR deep review with severity-tagged findings, inline comments, and a verdict; --survey runs a risk-tiered triage digest of what's safe to merge first.
github-monitor
Watch your GitHub repos across four views - a combined urgency monitor (stale PRs, new issues, releases), a new-issue triage queue, a release upgrade digest, or your own opened-PR tracker.
aeon-update
Pull framework updates from the upstream Aeon repo into this instance - 3-way merges canon's new commits into a PR, never clobbering operator config.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.