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 smicolon/ai-kit --skill worktree-managergit clone --depth 1 https://github.com/smicolon/ai-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/smicolon/ai-kit/worktree-manager)<a href="https://agentmods.dev/skills/smicolon/ai-kit/worktree-manager"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/worktree-manager/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/smicolon/ai-kit/worktree-manager"><img src="https://agentmods.dev/badge/skills/smicolon/ai-kit/worktree-manager.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.00077 | $0.01064 |
| Opus 5.5 | $0.00031 | $0.00426 |
| Sonnet 5.5 | $0.00015 | $0.00213 |
| Haiku 4.5 | $0.00008 | $0.00106 |
Grade A, and why
worktree-manager 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Manager Skill
Manages git worktrees for parallel development with automatic environment isolation.
Activation Triggers
This skill activates when the user:
- Asks about "worktree" or "git worktree"
- Mentions "wt" in context of git/branches
- Wants to "work on multiple branches simultaneously"
- Needs a "separate workspace for a feature"
- Asks about "parallel development" setup
- Wants to "set up a new branch workspace"
- Has "docker port conflicts" between branches
- Needs "database isolation" for parallel work
- Asks about ".worktreeinclude" or "env isolation"
Commands Reference
| Command | Alias | Description |
|---|---|---|
/wt create <branch> |
/wt c |
Create worktree with full isolation |
/wt list |
/wt ls |
Show all worktrees |
/wt remove <branch> |
/wt rm |
Remove worktree (stops Docker first) |
/wt open <branch> [--editor] |
/wt o |
Open (--cursor|-c, --agy|-a, --code|-v) |
Naming Convention
Worktrees are created as siblings with -- separator:
~/[PARENT_DIRECTORY]/[REPO_NAME]/ # main repo
~/[PARENT_DIRECTORY]/[REPO_NAME]--[BRANCH_NAME]/ # worktree for [BRANCH_NAME]
Three-Layer Isolation
Layer 1: .worktreeinclude — File Selection
Gitignore-style file at repo root controlling which untracked files to copy. Auto-generated with sensible defaults on first wt create.
.env*
# apps/*/.env*
[rewrite]
auto
[docker]
auto
Layer 2: [rewrite] — Env Var Isolation
auto: Suffixes DB_NAME, POSTGRES_DB, DATABASE_URL, COMPOSE_PROJECT_NAME with branch slug{{BRANCH}}: Template placeholder for custom vars
Layer 3: [docker] — Docker Compose Env Var Isolation
- Patches compose file with
${WT_PORT_*:-default}and${WT_CONTAINER_PREFIX:-default}syntax - Writes port/container env vars +
COMPOSE_PROJECT_NAMEto.env - Auto-creates databases in running Postgres
Auto-Setup Features
When creating a worktree, the following happens automatically:
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 · 114 lines · 77 tokens per session scan A 84f8b65871a6
worktree-manager is a skill published in the GitHub repository smicolon/ai-kit (6 stars, last pushed 1mo ago), licensed MIT. It adds 77 tokens to every session and 1,064 once invoked, about $0.0003 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
update-nanoclaw
Transactionally update a customized NanoClaw checkout from official upstream without exposing live mounted source, with fork-safe skill refresh, mutable-state snapshots, migration gates, exact-code upgrade markers, detected service restart, health verification, and automatic local rollback. Use for routine merge…
add-github
Add GitHub channel integration via Chat SDK. PR and issue comment threads as conversations.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
github-auth
Set up GitHub authentication for the agent using git (universally available) or the gh CLI. Covers HTTPS tokens, SSH keys, credential helpers, and gh auth — with a detection flow to pick the right method automatically.
github
Use gh as the primary interface for GitHub data and actions. Keep this skill focused on basic operations and command safety, not maintainer triage strategy.
updater_guide
Guidance for checking for and installing Row-Bot updates.