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/baphuongna/pi-crew/worktree-isolationnpx skills add baphuongna/pi-crew --skill worktree-isolationgit clone --depth 1 https://github.com/baphuongna/pi-crewWrote 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/baphuongna/pi-crew/worktree-isolation)<a href="https://agentmods.dev/skills/baphuongna/pi-crew/worktree-isolation"><img src="https://agentmods.dev/badge/skills/baphuongna/pi-crew/worktree-isolation.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.00012 | $0.01952 |
| Opus 5 | $0.00006 | $0.00976 |
| Sonnet 5 | $0.00002 | $0.00390 |
| Haiku 4.5 | $0.00001 | $0.00195 |
Grade A, and why
worktree-isolation 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 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.
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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
worktree-isolation
Use this skill for worktree-based execution or cleanup. Git worktrees create isolated working directories that allow parallel code-changing tasks without git conflicts.
How Worktrees Work
A git worktree is a separate working directory linked to the same repository. It has its own:
- Working directory (different path)
- HEAD (can be on a different branch)
- Staged/unstaged changes
But it shares:
- Object database (
.git/objects) - Refs (branches, tags)
This means creating a worktree is cheap (no clone needed) and fast.
When to Use Worktrees
Use worktree mode when:
- Running parallel implementation workers that modify the same repo
- Isolating risky changes that might need to be discarded
- Running multiple agents on the same codebase simultaneously
- Running a long task that would block other work
Don't use worktree mode when:
- The task is read-only (use scaffold mode instead)
- Only one agent needs to work at a time
- The repository has uncommitted changes (must be clean)
Worktree Lifecycle
1. Creation
Prerequisites:
- Leader repository must be clean (
git statusempty) - Sufficient disk space for worktree directory
Creation flow:
team-runner.ts (workspaceMode: "worktree")
→ prepareTaskWorkspace(manifest, task)
→ assertCleanLeader(repoRoot)
→ git worktree add <path> <branch>
→ linkNodeModulesIfPresent(repoRoot, worktreePath)
→ return { cwd: worktreePath, worktreePath, branch }
Naming convention:
- Branch:
crew/<sanitized-runId>-<sanitized-taskId> - Path:
.worktrees/<runId>/<taskId>/ - Deterministic from run/task IDs — no user-controlled fragments
Example:
Run: team_20260514092752_218fe358085d7115
Task: 01_explore
Branch: crew/team-20260514092752-218fe358085d7115/01-explore
Path: .worktrees/team-20260514092752-218fe358085d7115/01-explore/
2. Reuse
If a worktree with the same branch already exists, it is reused instead of recreated:
// Check if worktree already exists
const existing = git(cwd, ["worktree", "list", "--porcelain"]);
if (existing.includes(branch)) {
return { reused: true, worktreePath: parsePath(existing) };
}
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 · 238 lines · 12 tokens per session scan A fb64075f20e4
worktree-isolation is a skill published in the GitHub repository baphuongna/pi-crew (51 stars, last pushed 2d ago), licensed MIT. It adds 12 tokens to every session and 1,952 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…