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 fmind/dot --skill git-worktreegit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/git-worktree)<a href="https://agentmods.dev/skills/fmind/dot/git-worktree"><img src="https://agentmods.dev/badge/skills/fmind/dot/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.
<a href="https://agentmods.dev/skills/fmind/dot/git-worktree"><img src="https://agentmods.dev/badge/skills/fmind/dot/git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00020 | $0.00800 |
| Opus 5.5 | $0.00008 | $0.00320 |
| Sonnet 5.5 | $0.00004 | $0.00160 |
| Haiku 4.5 | $0.00002 | $0.00080 |
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 11d 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree
Choose a branch in the current checkout or an isolated workspace according to the task. A branch-only request needs no extra checkout and follows the branches guide; isolation, candidate identity, and cleanup follow the workflow below.
Workflow
- Record the source: inspect
git status --short,git diff,git diff --cached,git rev-parse HEAD, andgit worktree list --porcelain. Identify whether the candidate is a commit, the index, or selected working-tree changes. - Choose isolation: use a linked worktree for a committed revision or new branch. Use the dirty candidate procedure when validation must include uncommitted files, or when checks must not share Git refs or hooks with the source.
- Create a fresh destination: choose a new sibling or temporary path outside the source. For a read-only review of committed code, use
git worktree add --detach <destination> <revision>; for implementation, usegit worktree add -b <new-branch> <destination> <base>. - Inspect execution inputs: read the destination's tasks and hooks before running them; isolate virtual environments, build output, coverage, ports, databases, and caches that tests mutate. Do not copy credentials or reuse a live database to make a fixture pass.
- Run the owning gate: invoke the project's commands from the destination. Formatter output changes the tested candidate; compare it with the intended source before transferring proof or applying any resulting edits.
- Return only intended changes: review the destination diff, transfer task-owned changes when authorized, and preserve the source index. Commits, pushes, and merges follow the user's requested delivery flow.
- Clean up deliberately: inspect destination status and recover useful artifacts first. Use
git worktree remove <destination>for an owned clean linked worktree; retain a dirty one until its changes are accounted for. Remove only the recorded disposable clone for a copied candidate. - Report identity: revision, included dirty changes, executed gate, source-versus-tested differences, and any retained workspace.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago Changed 99c8c3156ca1
- 12d ago Changed · +8 lines · -2 tokens per session 36bed29ea4d7
- 23d ago Changed fd27c5e54415
- 29d ago Changed · +1 lines · -12 tokens per session 9cd1ecc96c5d
- 1mo ago Changed · +1 tokens per session 3b0468c09c9f
- 1mo ago First seen · 38 lines · 33 tokens per session scan A e268afe315b8
git-worktree is a skill published in the GitHub repository fmind/dot (11 stars, last pushed yesterday), licensed MIT. It adds 20 tokens to every session and 800 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-09-10.
Other skills, from other repositories
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
git-add-commit-push
Stage, commit (Conventional Commits), and push in one flow, auto-healing lefthook pre-commit and pre-push failures. Use when committing and pushing work end-to-end.
github-repository
Configure a GitHub repository's metadata (description, homepage, topics) and solo-developer settings via gh, derived from the codebase. Use when setting up or tidying a repo's GitHub settings.
lefthook
Canonical lefthook git-hooks setup — pre-commit (format, check, secret scan) and pre-push (test), each delegating to mise run tasks. Use when configuring or debugging git hooks.
github-issues
Manage GitHub issues with gh: confirm repo and state, deduplicate, preserve evidence, and verify authorized creation, edits, labels, comments, or closure.
github-pull-request
Create or update a GitHub pull request with a structured What / Why / How / Test-plan body. Use when opening or updating a PR for the current branch.