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/techdufus/oh-my-claude/worktreenpx skills add TechDufus/oh-my-claude --skill worktreegit clone --depth 1 https://github.com/TechDufus/oh-my-claudeWrote 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/techdufus/oh-my-claude/worktree)<a href="https://agentmods.dev/skills/techdufus/oh-my-claude/worktree"><img src="https://agentmods.dev/badge/skills/techdufus/oh-my-claude/worktree.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.1 | $0.00039 | $0.03713 |
| Opus 5 | $0.00019 | $0.01857 |
| Sonnet 5 | $0.00008 | $0.00743 |
| Haiku 4.5 | $0.00004 | $0.00371 |
Grade C, and why
worktree scanned grade C with 1 finding 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 6d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
$ rm -rf .worktrees/auth-feature How it starts
The opening of the file, as written. The whole thing — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Skill
Git worktree automation for isolated feature development.
When This Skill Activates
| Category | Trigger Phrases |
|---|---|
| Create worktree | /worktree create <name>, /worktree new <name> |
| List worktrees | /worktree list, /worktree ls |
| Remove worktree | /worktree remove <name>, /worktree rm <name> |
| Status | /worktree status |
Commands
Create Worktree
/worktree create <feature-name>
Creates an isolated worktree for feature development.
Workflow:
- Generate branch name:
feat/<feature-name> - Create worktree:
git worktree add .worktrees/<feature-name> -b feat/<feature-name> - Copy environment files (if they exist):
.env,.env.local,.env.development.nvmrc,.node-version.npmrc
- Detect and run package manager install:
- If
package-lock.json→npm install - If
yarn.lock→yarn install - If
pnpm-lock.yaml→pnpm install - If
bun.lockb→bun install
- If
- Add
.worktrees/to.gitignoreif not present - Verify worktree creation:
- Run
git -C .worktrees/<name> statusto confirm clean state - Run
git worktree listto confirm worktree is registered - If verification fails, run cleanup and report error
- Run
- Report path and instructions
Example:
git worktree add .worktrees/auth-feature -b feat/auth-feature
cp .env .worktrees/auth-feature/ 2>/dev/null || true
cp .nvmrc .worktrees/auth-feature/ 2>/dev/null || true
cd .worktrees/auth-feature && npm install
List Worktrees
/worktree list
Shows all active worktrees:
git worktree list
Remove Worktree
/worktree remove <name>
Removes a worktree and optionally its branch:
Workflow:
- Confirm removal with user
- Remove worktree:
git worktree remove .worktrees/<name> --force - Ask if branch should be deleted
- If yes:
git branch -D feat/<name>
Status
/worktree status
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.
- 6d ago First seen · 537 lines · 39 tokens per session scan C 291ee1b5e437
worktree is a skill published in the GitHub repository TechDufus/oh-my-claude (176 stars, last pushed 1mo ago), licensed MIT. It adds 39 tokens to every session and 3,713 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.
flow-next-tracker-sync
Project a flow-next spec to a tracker issue (Linear, GitHub, GitLab, Jira) and reconcile two-way. Use when asked to sync to a tracker. NOT plan-sync.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步（architecture-sync）。OpenCode / Claude / Codex / Cursor 通用。.
taiyi-diagram-c4
TaiyiForge 辅助 — 从代码反推 C4 架构文档（Observed/Inferred 分层 · Mermaid 真源）。OpenCode / Claude / Codex / Cursor 通用。.
flow-next-prime
Assess codebase agent and production readiness. Classifies the project, verifies commands run, leads with a verdict and ranked next actions.