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 soulcodex/agentic --skill git-worktree-workspacesgit clone --depth 1 https://github.com/soulcodex/agenticWrote 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/soulcodex/agentic/git-worktree-workspaces)<a href="https://agentmods.dev/skills/soulcodex/agentic/git-worktree-workspaces"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/git-worktree-workspaces/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/soulcodex/agentic/git-worktree-workspaces"><img src="https://agentmods.dev/badge/skills/soulcodex/agentic/git-worktree-workspaces.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.00782 |
| Opus 5.5 | $0.00023 | $0.00313 |
| Sonnet 5.5 | $0.00012 | $0.00156 |
| Haiku 4.5 | $0.00006 | $0.00078 |
Grade A, and why
git-worktree-workspaces 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Workspaces Skill
Step 1 — Discover Current Repo State
git rev-parse --show-toplevel
git branch --show-current
git worktree list --porcelain
git remote show origin | sed -n '/HEAD branch/s/.*: //p'
Capture:
- Current repository root and active branch
- Existing worktrees and paths
- Remote default branch (do not assume a fixed branch name)
Step 2 — Pick Naming and Layout
Use a predictable directory pattern outside the main working tree:
REPO_ROOT="$(git rev-parse --show-toplevel)"
REPO_NAME="$(basename "$REPO_ROOT")"
WORKTREE_ROOT="$(dirname "$REPO_ROOT")/${REPO_NAME}-worktrees"
mkdir -p "$WORKTREE_ROOT"
Recommended names:
- Branch:
feat/<topic>,fix/<topic>,docs/<topic> - Path:
$WORKTREE_ROOT/<branch-slug>
Step 3 — Create a New Worktree
For a new branch:
BASE_BRANCH="$(git remote show origin | sed -n '/HEAD branch/s/.*: //p')"
NEW_BRANCH="feat/<topic>"
TARGET_PATH="$WORKTREE_ROOT/${NEW_BRANCH//\//-}"
git fetch origin "$BASE_BRANCH"
git worktree add -b "$NEW_BRANCH" "$TARGET_PATH" "origin/$BASE_BRANCH"
For an existing branch:
EXISTING_BRANCH="<branch>"
TARGET_PATH="$WORKTREE_ROOT/${EXISTING_BRANCH//\//-}"
git fetch origin
git worktree add "$TARGET_PATH" "$EXISTING_BRANCH"
Step 4 — Work Independently Per Task
Inside each worktree:
cd "$TARGET_PATH"
git status --short
git add <files>
git commit -m "feat(<scope>): <summary>"
Rules:
- One task per worktree branch.
- Keep commits scoped to that task only.
- Run project quality gates before pushing.
Step 5 — Push and Open PRs
git push -u origin "$(git branch --show-current)"
gh pr create --base "<base-branch>" --head "$(git branch --show-current)"
Use Refs #<issue> for stacked/chained PRs that should not auto-close yet.
Use Closes #<issue> only on the final PR intended to close the issue on merge.
Step 6 — Safe Cleanup (Local Only)
After a branch is merged and no longer needed locally:
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 · 121 lines · 58 tokens per session scan A 1569acbb9cbd
git-worktree-workspaces is a skill published in the GitHub repository soulcodex/agentic (10 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 782 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
github-multi-repo
Multi-repository coordination, synchronization, and architecture management across many GitHub repos. Use when changes span several repositories, keeping repos in sync, or planning cross-repo architecture and dependency work.
hatch3r-cli-fd
User-friendly find replacement, gitignore-aware. Use when locating filenames or directories by glob with parallel walking; invoke fd. Outputs newline-separated hit records; bound results with -c or --max-count.
hatch3r-handoff-resume
Loads and resumes a handoff document from .hatch3r/handoffs/active/. Validates schema, integrity, expiry, and gitref drift before surfacing content as user-tier context.
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern. For many independent single-turn transforms (translate/rewrite/extract each file into a new file) that can wait…
batch-api
Prepare a many-file, single-turn transform (translate, rewrite, extract) as a plan and submit it to the asynchronous, half-price DashScope Batch API; results are delivered as new files hours later. Invoke explicitly with /batch-api.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.