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 djscheuf/agentic-dev-ecosystem-template --skill git-worktreegit clone --depth 1 https://github.com/djscheuf/agentic-dev-ecosystem-templateWrote 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/djscheuf/agentic-dev-ecosystem-template/git-worktree)<a href="https://agentmods.dev/skills/djscheuf/agentic-dev-ecosystem-template/git-worktree"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/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/djscheuf/agentic-dev-ecosystem-template/git-worktree"><img src="https://agentmods.dev/badge/skills/djscheuf/agentic-dev-ecosystem-template/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.00018 | $0.00432 |
| Opus 5.5 | $0.00007 | $0.00173 |
| Sonnet 5.5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
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 22d 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.
What it actually says
git worktree
git worktree lets a single repository maintain multiple working trees, each checked out to a different branch or commit. Use it when you need to work on multiple branches at once (e.g., a hotfix alongside a long-running refactor) without stashing or cloning the repository again.
When to use this skill
- Creating a new linked worktree from a branch, tag, or detached commit.
- Listing, moving, locking, unlocking, or removing existing worktrees.
- Cleaning up stale worktree metadata after manual deletion.
- Repairing broken worktree links after moving repositories or worktrees.
- Configuring per-worktree Git settings.
Core concepts
- A repository has one main worktree (unless it is bare) and zero or more linked worktrees.
- All worktrees share the same object database and most refs, but each has its own
HEAD,index, and checked-out files. - A worktree is identified by its path (relative or absolute); if the path tail is unique, you can refer to it by just the basename.
- Worktree metadata lives under
$GIT_DIR/worktrees/<id>/.
Reference Files
ref/commands.md— subcommand syntax, options, and machine-readablelistoutput format.ref/configuration.md— shared vs. per-worktree config and relevantgit-configvariables.ref/troubleshooting.md— repair scenarios, cleanup, locks, and common gotchas.
Utility Scripts
scripts/create_worktree.sh— create a linked worktree for a branch at the conventional path{parent}/worktrees/{repo}_{branch}. Supports--dry-run.scripts/clean_worktree.sh— remove the worktree for a branch after confirming the branch is merged; optionally delete the branch. Supports--dry-runand--force.
[Source: https://git-scm.com/docs/git-worktree]
What ships with it
5 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.
- 22d ago First seen · 36 lines · 18 tokens per session scan A 20b66a4bf353
git-worktree is a skill published in the GitHub repository djscheuf/agentic-dev-ecosystem-template (12 stars, last pushed 20d ago), licensed MIT. It adds 18 tokens to every session and 432 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-10-01.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.