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 agentmods add skills/ufomiao/zcf/git-worktreenpx skills add UfoMiao/zcf --skill git-worktreegit clone --depth 1 https://github.com/UfoMiao/zcfWhat 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 | $0.00028 | $0.02343 |
| Opus 5 | $0.00014 | $0.01171 |
| Sonnet 5 | $0.00006 | $0.00469 |
| Haiku 4.5 | $0.00003 | $0.00234 |
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 2d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Command: Git Worktree
Manage Git worktrees with smart defaults, IDE integration and content migration in structured ../.zcf/project-name/ paths.
Execute commands directly and provide concise results.
Usage
# Basic operations
/git-worktree add <path> # create new branch named <path> from main/master
/git-worktree add <path> -b <branch> # create new branch with specified name
/git-worktree add <path> -o # create and open directly in IDE
/git-worktree list # show all worktree status
/git-worktree remove <path> # remove specified worktree
/git-worktree prune # clean invalid worktree references
# Content migration
/git-worktree migrate <target> --from <source> # migrate uncommitted content
/git-worktree migrate <target> --stash # migrate stash content
Options
| Option | Description |
|---|---|
add [<path>] |
Add new worktree in ../.zcf/project-name/<path> |
migrate <target> |
Migrate content to specified worktree |
list |
List all worktrees and their status |
remove <path> |
Remove worktree at specified path |
prune |
Clean invalid worktree references |
-b <branch> |
Create new branch and checkout to worktree |
-o, --open |
Open directly in IDE after creation (skip prompt) |
--from <source> |
Specify migration source path (migrate only) |
--stash |
Migrate current stash content (migrate only) |
--track |
Set new branch to track corresponding remote branch |
--guess-remote |
Auto guess remote branch for tracking |
--detach |
Create detached HEAD worktree |
--checkout |
Checkout immediately after creation (default behavior) |
--lock |
Lock worktree after creation |
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.
- 2d ago First seen · 272 lines · 28 tokens per session scan A ea4dbd731daa
git-worktree is a skill published in the GitHub repository UfoMiao/zcf (6,081 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 2,343 once invoked, about $0.0001 per session on Opus 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.
Other skills, from other repositories
golden-rss
Use when testing the rss golden build.
design-system-builder
Extract design systems from reference UI images and generate implementation-ready UI design prompts. Use when users provide UI screenshots/mockups and want to create consistent designs, generate design systems, or build MVP UIs matching reference aesthetics.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
agent-memory
../../../engineering/agent-memory/skills/agent-memory/SKILL.md.
agile-product-owner
../../../product-team/agile-product-owner/skills/agile-product-owner/SKILL.md.