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 skywalkercyt/mp-implement --skill using-git-worktreesgit clone --depth 1 https://github.com/skywalkercyt/mp-implementWrote 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/skywalkercyt/mp-implement/using-git-worktrees)<a href="https://agentmods.dev/skills/skywalkercyt/mp-implement/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/using-git-worktrees/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/skywalkercyt/mp-implement/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/skywalkercyt/mp-implement/using-git-worktrees.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.00041 | $0.00697 |
| Opus 5.5 | $0.00016 | $0.00279 |
| Sonnet 5.5 | $0.00008 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
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 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Adapted skill — discipline originating in Superpowers v5.1.0 (MIT, Jesse Vincent), rewritten in mattpocock-skills style. Used by
/mp-implement-issuestep 3 and both pipelines' Phase 3 to give each slice an isolated workspace.
Isolate the work before touching code: detect existing isolation first, use the harness's native worktree tool if one exists, fall back to git worktree only without one.
1. Detect existing isolation
Run detection before creating anything.
GIT_DIR=$(cd "$(git rev-parse --git-dir)" && pwd -P)
GIT_COMMON=$(cd "$(git rev-parse --git-common-dir)" && pwd -P)
git rev-parse --show-superproject-working-tree 2>/dev/null
GIT_DIR != GIT_COMMONand the superproject check prints nothing → already in a linked worktree; skip to setup (step 3). On detached HEAD, note the worktree is externally managed and branch creation happens at finish time.- The superproject check prints a path → you're in a submodule; treat it as a normal repo.
In a normal checkout, honor any declared worktree preference without asking. With none declared, ask one consent question; declined → work in place and skip to setup.
2. Create the worktree
Native tool first. If the harness offers one (EnterWorktree-style tool, /worktree command, --worktree flag), use it — it manages placement, branching, and cleanup that the git fallback leaves to you. Then skip to setup.
Git fallback — only with no native tool. Directory priority: declared preference > existing .worktrees/ or worktrees/ (.worktrees/ wins if both) > default .worktrees/ at the repo root.
Verify the directory is git-ignored before creating:
git check-ignore -q <dir> || echo "<dir>/" >> .git/info/exclude
git worktree add .worktrees/<branch> -b <branch>
cd .worktrees/<branch>
A permission error here means the sandbox blocked creation — say so, then run setup and baseline in place.
3. Setup
Auto-detect and install:
[ -f package.json ] && npm install
[ -f Cargo.toml ] && cargo build
[ -f requirements.txt ] && pip install -r requirements.txt
[ -f pyproject.toml ] && poetry install
[ -f go.mod ] && go mod download
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 · 69 lines · 41 tokens per session scan A 225fcf34d458
using-git-worktrees is a skill published in the GitHub repository skywalkercyt/mp-implement (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 697 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…