AICodingFlow: Skill for Claude Code

.agents/skills/git-worktree/SKILL.md

git-worktree is a skill for Claude Code, Codex from Terry-Mao/AICodingFlow. It costs 18 tokens per session (433 once invoked), scanned A, original, MIT.

A Git worktree setup guide for creating a separate working directory linked to another branch.

In plain words
What is it for?
It helps check repository safety, choose a base branch, create a compliant branch and worktree, and avoid overwriting existing work.
Why use it?
It keeps parallel development isolated so changes in one task do not disturb the current working directory.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is Terry-Mao/AICodingFlow's own configuration. It tells Claude Code and Codex how to work on AICodingFlow 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 AICodingFlow configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Terry-Mao/AICodingFlow. 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/Terry-Mao/AICodingFlow/main/.agents/skills/git-worktree/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Terry-Mao/AICodingFlow

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 git-worktree

README.md
[![agentmods](https://agentmods.dev/badge/skills/terry-mao/aicodingflow/git-worktree/github.svg)](https://agentmods.dev/skills/terry-mao/aicodingflow/git-worktree)
Your own site
<a href="https://agentmods.dev/skills/terry-mao/aicodingflow/git-worktree"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/git-worktree/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 git-worktree

Your own site · 80×15
<a href="https://agentmods.dev/skills/terry-mao/aicodingflow/git-worktree"><img src="https://agentmods.dev/badge/skills/terry-mao/aicodingflow/git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 433 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found 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.00018 $0.00433
Opus 5.5 $0.00007 $0.00173
Sonnet 5.5 $0.00004 $0.00087
Haiku 4.5 $0.00002 $0.00043

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

Security

Grade A, and why

git-worktree 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.

.agents/skills/git-worktree/SKILL.md · 45 lines

What it actually says

git-worktree

Use this when work should not disturb the current worktree. The new worktree does not copy uncommitted changes, and it does not change the user's shell directory.

Naming and base

Use the git-branch naming rules: issue work is <type>/<short-desc>-<issueID>, other work uses a user-provided name, and no issue ID is invented. When an issue ID is provided, use one gh issue view call for naming context and continue from the request if it fails. Store the worktree at .worktrees/<branch-name> so branch path segments are preserved. The repository should ignore .worktrees/.

Default the base to main; same-repository work prefers origin/<base>, then local <base>, and uses upstream only for fork workflows or explicit guidance. Fetch/check freshness only when it affects the result. If the local base is stale, confirm before using it or create from a fetched remote base and report that the local base was unchanged.

Create

Before creating, check current status, existing worktrees/branches, and the target path. Stop if any target already exists or dirty-work intent is unclear. Validate the branch with git check-ref-format --branch <branch-name>, create parent directories as needed, then run the equivalent of:

git worktree add --no-track -b <branch-name> .worktrees/<branch-name> <base-ref>

Verify the new worktree's branch, status, and pwd. Report its path, base, whether dirty changes were excluded, and the user's next step: cd .worktrees/<branch-name>.

Do not remove, prune, overwrite, reset, stash, push, or force anything unless explicitly asked. Do not create protected/shared base branches as targets. Subsequent agent work uses the new worktree unless the user says otherwise.

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 · 45 lines · 18 tokens per session scan A 9844b1ba1005

Subscribe to this mod's changes

git-worktree is a skill published in the GitHub repository Terry-Mao/AICodingFlow (169 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 433 once invoked, about $0.0001 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-30.