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/lfyxhappy/lfcode/worktreenpx skills add lfyxhappy/lfcode --skill worktreegit clone --depth 1 https://github.com/lfyxhappy/lfcodeWhat 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.00035 | $0.02166 |
| Opus 5 | $0.00017 | $0.01083 |
| Sonnet 5 | $0.00007 | $0.00433 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
compose: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 yesterday.
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
100% identical to compose:worktree — 0 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 — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Overview
Ensure work happens in an isolated workspace. Prefer your platform's native worktree tools. Fall back to manual git worktrees only when no native tool is available.
Core principle: Detect existing isolation first. Then use native tools. Then fall back to git. Never fight the harness.
Announce at start: "I'm using the compose:worktree skill to set up an isolated workspace."
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 3 (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: "Already in isolated workspace at
<path>(detached HEAD, externally managed). Branch creation needed at finish time."
If GIT_DIR == GIT_COMMON (or in a submodule): You are in a normal repo checkout.
-
Check memory for a
worktree-consentpreference in thecompose-preferencesmemory file, or check your instructions for a declared worktree preference. If either exists, honor it silently. -
If no saved preference, use
compose:ask:- header:
Worktree - question:
Set up an isolated worktree? It protects your current branch from changes. - options:
- label:
Yes (Recommended), description:Create an isolated worktree for this work - label:
No, description:Work directly on the current branch - label:
Always use worktrees, description:Use worktrees now and remember for future sessions - label:
Never use worktrees, description:Work in place now and remember for future sessions
- label:
- header:
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.
- yesterday First seen · 235 lines · 35 tokens per session scan A b01cea730763
compose:worktree is a skill published in the GitHub repository lfyxhappy/lfcode (2 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 2,166 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to compose:worktree, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
Review a GitHub PR (via gh)
Review a specific GitHub pull request with gh — fetch the diff, fan out reviewers, consolidate, and optionally post the review. Requires the gh CLI or the GitHub MCP server.
Implement (multi-agent loop)
Orchestrate an implement -> review -> fix loop with subagents until reviewers sign off.
Best of N (parallel attempts)
Delegate N parallel subagents on the same task, then pick the best result.
Check work (verify against criteria)
Verify an implementation against acceptance criteria with a reviewer and a tester.
Commit (clean, conventional)
Stage the right changes and write a clear, conventional commit message.
Design doc (write -> review loop)
Draft a design document and iterate writer/reviewer subagents until consensus.