mindforge-workspace-isolated

mindforge-workspace-isolated is a skill for Claude Code, Codex from sairam0424/MindForge. It costs 36 tokens per session (1,350 once invoked), scanned A, a copy of using-git-worktrees, MIT.

A workflow for creating an isolated Git worktree before feature work or planned implementation. A Git worktree is a separate working directory connected to the same repository, so multiple branches can be worked on at once.

In plain words
What is it for?
It is for starting feature work safely, working on several branches at the same time, and executing implementation plans without disturbing the existing checkout.
Why use it?
It keeps new changes separate from the current workspace and branch. The setup checks directory choices and ignore rules before creating the isolated copy.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions CLAUDE.md.

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.

Good fit It is for starting feature work safely, working on several branches at the same time, and executing implementation plans without disturbing the existing checkout.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.

Made for: Claude Code, Codex.

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 mindforge-workspace-isolated

README.md
[![agentmods](https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-workspace-isolated/github.svg)](https://agentmods.dev/skills/sairam0424/mindforge/mindforge-workspace-isolated)
Your own site
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-workspace-isolated"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-workspace-isolated/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 mindforge-workspace-isolated

Your own site · 80×15
<a href="https://agentmods.dev/skills/sairam0424/mindforge/mindforge-workspace-isolated"><img src="https://agentmods.dev/badge/skills/sairam0424/mindforge/mindforge-workspace-isolated.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,350 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 88% 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.00036 $0.01350
Opus 5 $0.00018 $0.00675
Sonnet 5 $0.00007 $0.00270
Haiku 4.5 $0.00004 $0.00135

Measured 6d ago against content hash 1917d670b47d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

mindforge-workspace-isolated 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.

Origin

This is a copy

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

.agent/skills/mindforge-workspace-isolated/SKILL.md · 219 lines

How it starts

The opening of the file, as written. The whole thing — 219 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/mindforge/worktrees/<project-name>/ (global location)

Which would you prefer?

Safety Verification

For Project-Local Directories (.worktrees or worktrees)

MUST verify directory is ignored before creating worktree:

# Check if directory is ignored (respects local, global, and system gitignore)
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null

If NOT ignored:

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/mindforge/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/mindforge/worktrees/*)
    path="~/.config/mindforge/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 · 219 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. 6d ago First seen · 219 lines · 36 tokens per session scan A 1917d670b47d

Subscribe to this mod's changes

mindforge-workspace-isolated is a skill published in the GitHub repository sairam0424/MindForge (0 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 1,350 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to using-git-worktrees, differing in 18 lines, and is treated as a copy.

Related

Other skills, from other repositories

linear-cli

Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.

Peiiii/nextclaw · 45 tokens

changelog-generator

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

ComposioHQ/awesome-claude-skills · 48 tokens

openclaw-github-dedupe

Investigate a cluster of GitHub issues and PRs, determine canonical candidates, post duplicate/related status, preserve contributor credit, and execute cleanup actions. Supports autonomous mode for provided-link-only closeout, merge/fix follow-through, changelog, and post-merge issue/PR cleanup.

vincentkoc/dotskills · 68 tokens

openclaw-pr-batch-sweep

Select, review, repair, validate, and land batches of up to 20 low-risk OpenClaw contributor pull requests using Vincent's maintainer preferences and bounded sub-agent lanes. Use for "next 20", broad contributor PR sweeps, merge-candidate mining, or continued PR-batch work where drafts, maintainer work, trivial…

vincentkoc/dotskills · 95 tokens

org-branch-cleanup

Audit and safely prune stale branches across a GitHub organization with immutable snapshots, conservative merged-PR classification, live SHA/protection/open-PR revalidation, resumable deletion ledgers, and post-delete verification. Use when a maintainer asks to clean up old, dead, merged, bot-created, or abandoned…

vincentkoc/dotskills · 91 tokens

github-airplane-mode

Inspect or switch the local Git and GitHub download guard using an already-installed compatible low-data command. Use for airplane mode, flight or metered connections, returning online, or requests to enable, disable, or automatically select low-data protection on this machine.

vincentkoc/dotskills · 56 tokens