phantom-neural-cortex: Skill for Claude Code

.claude/skills/using-git-worktrees/SKILL.md

using-git-worktrees is a skill for Claude Code from LEEI1337/phantom-neural-cortex. It costs 35 tokens per session (1,334 once invoked), scanned A, a copy of using-git-worktrees, MIT.

A workflow for using Git worktrees, which are separate working folders for different branches of the same Git repository.

In plain words
What is it for?
Use it when starting a feature or implementation plan that needs its own folder and branch.
Why use it?
It keeps feature work isolated from the current workspace, reducing accidental changes to unrelated files or branches.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md; mentions subagents.

This is LEEI1337/phantom-neural-cortex's own configuration. It tells Claude Code how to work on phantom-neural-cortex itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything phantom-neural-cortex configures →

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/jesse/myproject/.worktrees/auth.

Reuse

Borrowing it

Nothing to install: this file belongs to LEEI1337/phantom-neural-cortex. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/LEEI1337/phantom-neural-cortex/master/.claude/skills/using-git-worktrees/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/LEEI1337/phantom-neural-cortex

Made for: Claude Code.

Wrote 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.

agentmods badge for using-git-worktrees

README.md
[![agentmods](https://agentmods.dev/badge/skills/leei1337/phantom-neural-cortex/using-git-worktrees/github.svg)](https://agentmods.dev/skills/leei1337/phantom-neural-cortex/using-git-worktrees)
Your own site
<a href="https://agentmods.dev/skills/leei1337/phantom-neural-cortex/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/leei1337/phantom-neural-cortex/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.

agentmods 80×15 button for using-git-worktrees

Your own site · 80×15
<a href="https://agentmods.dev/skills/leei1337/phantom-neural-cortex/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/leei1337/phantom-neural-cortex/using-git-worktrees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,334 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 84% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00035 $0.01334
Opus 5.5 $0.00014 $0.00534
Sonnet 5.5 $0.00007 $0.00267
Haiku 4.5 $0.00003 $0.00133

Measured 1mo ago against content hash 29571961ff48, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

This is a copy

84% identical to using-git-worktrees — 37 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.

.claude/skills/using-git-worktrees/SKILL.md · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Using Git Worktrees

Overview

Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.

Core principle: Systematic directory selection + safety verification = reliable isolation.

Announce at start: "I'm using the using-git-worktrees skill to set up an isolated workspace."

Directory Selection Process

Follow this priority order:

1. Check Existing Directories

# Check in priority order
ls -d .worktrees 2>/dev/null     # Preferred (hidden)
ls -d worktrees 2>/dev/null      # Alternative

If found: Use that directory. If both exist, .worktrees wins.

2. Check CLAUDE.md

grep -i "worktree.*director" CLAUDE.md 2>/dev/null

If preference specified: Use it without asking.

3. Ask User

If no directory exists and no CLAUDE.md preference:

No worktree directory found. Where should I create worktrees?

1. .worktrees/ (project-local, hidden)
2. ~/.config/superpowers/worktrees/<project-name>/ (global location)

Which would you prefer?

Safety Verification

For Project-Local Directories (.worktrees or worktrees)

MUST verify .gitignore before creating worktree:

# Check if directory pattern in .gitignore
grep -q "^\.worktrees/$" .gitignore || grep -q "^worktrees/$" .gitignore

If NOT in .gitignore:

Per Jesse's rule "Fix broken things immediately":

  1. Add appropriate line to .gitignore
  2. Commit the change
  3. Proceed with worktree creation

Why critical: Prevents accidentally committing worktree contents to repository.

For Global Directory (~/.config/superpowers/worktrees)

No .gitignore verification needed - outside project entirely.

Creation Steps

1. Detect Project Name

project=$(basename "$(git rev-parse --show-toplevel)")

2. Create Worktree

# Determine full path
case $LOCATION in
  .worktrees|worktrees)
    path="$LOCATION/$BRANCH_NAME"
    ;;
  ~/.config/superpowers/worktrees/*)
    path="~/.config/superpowers/worktrees/$project/$BRANCH_NAME"
    ;;
esac

# Create worktree with new branch
git worktree add "$path" -b "$BRANCH_NAME"
cd "$path"

Read the full file on GitHub · 214 lines

Changes

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.

  1. 1mo ago First seen · 214 lines · 35 tokens per session scan A 29571961ff48

Subscribe to this mod's changes

using-git-worktrees is a skill published in the GitHub repository LEEI1337/phantom-neural-cortex (5 stars, last pushed 7mo ago), licensed MIT. It adds 35 tokens to every session and 1,334 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 84% identical to using-git-worktrees, differing in 37 lines, and is treated as a copy.

Related

Other skills, from other repositories

release

Cut a logseq-brain release — eval gate, version bump in plugin.json and BRAINVERSION, tag, GitHub release, .plugin rebuild, skillsmith marketplace bump. Invoke only when the user asks to release.

jame581/LogseqBrain · 47 tokens

standup

Facilitate a read-only standup across git worktrees, branches, or PRs to compare changes and produce one consolidation plan.

thedotmack/claude-mem · 30 tokens

version-bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…

thedotmack/claude-mem · 64 tokens

prs

Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.

google-gemini/gemini-cli · 27 tokens

release

Use this skill for EVERY ClawRouter release. Enforces the full checklist — version sync, CHANGELOG, build, tests, npm publish, git tag, GitHub release. No step can be skipped.

BlockRunAI/ClawRouter · 44 tokens

spec-kitty-git-workflow

Understand how Spec Kitty manages git: what git operations Python handles automatically, what agents must do manually, worktree lifecycle, auto-commit behavior, merge execution, and the safe-commit pattern. Triggers: "how does spec-kitty use git", "worktree management", "auto-commit", "who commits what", "git…

Priivacy-ai/spec-kitty · 125 tokens