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/eilodon/dps-superskills-mcp/using-git-worktreesnpx skills add Eilodon/DPS-Superskills-MCP --skill using-git-worktreesgit clone --depth 1 https://github.com/Eilodon/DPS-Superskills-MCPWrote 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/eilodon/dps-superskills-mcp/using-git-worktrees)<a href="https://agentmods.dev/skills/eilodon/dps-superskills-mcp/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/eilodon/dps-superskills-mcp/using-git-worktrees.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 | $0.00041 | $0.01351 |
| Opus 5 | $0.00020 | $0.00675 |
| Sonnet 5 | $0.00008 | $0.00270 |
| Haiku 4.5 | $0.00004 | $0.00135 |
Grade A, and why
using-git-worktrees 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 4d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Ensure work happens in an isolated workspace. Prefer native harness tools. Fall back to git worktrees only when no native tool is available.
Core principle: Detect isolation first. Use native tools. Then fall back to git. Never fight the harness.
Announce: "Using using-git-worktrees to set up an isolated workspace."
Pre-Check: Harness Capability
Read docs/superskills/.skill-init before creating anything:
cat docs/superskills/.skill-init 2>/dev/null || echo "skill-init not run — run it first"
Check TASK_TOOL field. If TASK_TOOL: NO → subagent dispatch won't work in this harness.
Check HARNESS field — affects which native worktree tool to try in Step 1a.
Step 0: Detect Existing Isolation
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 rev-parse --show-superproject-working-tree 2>/dev/null
# If this returns a path → you're in a submodule, treat as normal repo
If GIT_DIR != GIT_COMMON (and not submodule): Already in linked worktree → skip to Step 3.
Report:
- On branch: "Already in isolated workspace at
<path>on branch<name>." - Detached HEAD: "Already in isolated workspace (detached HEAD, externally managed)."
If GIT_DIR == GIT_COMMON: Normal repo. Ask consent before creating worktree:
"Would you like me to set up an isolated worktree? It protects your current branch."
Honor any existing preference without asking again. If user declines → skip to Step 3.
Step 1: Create Isolated Workspace
1a. Native Worktree Tool (preferred)
Check for: EnterWorktree, WorktreeCreate, /worktree, --worktree.
If available → use it. Skip to Step 3.
Using git worktree add when a native tool exists creates phantom state. Don't.
1b. Git Worktree Fallback (only if no native tool)
Directory selection (priority order):
- User-declared preference in instructions → use it
.worktrees/exists at project root → use it (verify ignored)worktrees/exists → use it (verify ignored)~/.config/superskills/worktrees/<project>/exists → use it- No guidance → default to
.worktrees/
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 163 lines · 41 tokens per session scan A 0ad4b223c917
using-git-worktrees is a skill published in the GitHub repository Eilodon/DPS-Superskills-MCP (0 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 41 tokens to every session and 1,351 once invoked, about $0.0002 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-31.
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…
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…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…