agentmods.dev

dev:worktree

dev:worktree is a skill for Claude Code from atournayre/claude-marketplace. It costs 13 tokens per session (620 once invoked), scanned A, original, MIT.

A workflow for managing Git worktrees, which are separate working folders connected to one Git repository. It supports developing multiple features in parallel.

In plain words
What is it for?
Create, list, and remove worktrees for features or hotfixes, with folders stored under .worktrees and tracking metadata saved in a JSON file.
Why use it?
It keeps parallel feature work in separate folders and branches, reducing the need to constantly switch branches and helping avoid conflicts.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: model in frontmatter; names the AskUserQuestion tool.

Part of the dev plugin — 25 skills, 8 agents shipped together

not rated 9repo 6mo ago A scan 13 tokens original MIT

Good fit Create, list, and remove worktrees for features or hotfixes, with folders stored under .worktrees and tracking metadata saved in a JSON file.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/atournayre/claude-marketplace/worktree
View source ↗ atournayre/claude-marketplace atournayre.github.io
Install

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.

Any agent
npx skills add atournayre/claude-marketplace --skill worktree
Clone the repo
git clone --depth 1 https://github.com/atournayre/claude-marketplace

Made for: Claude Code.

Or install dev, the plugin that ships this one along with the rest of its 25 skills, 8 agents.

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 dev:worktree

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/atournayre/claude-marketplace/worktree"><img src="https://agentmods.dev/badge/skills/atournayre/claude-marketplace/worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 620 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 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.00013 $0.00620
Opus 5 $0.00006 $0.00310
Sonnet 5 $0.00003 $0.00124
Haiku 4.5 $0.00001 $0.00062

Measured 12d ago against content hash 14d60c704674, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

dev: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 12d 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.

dev/skills/worktree/SKILL.md · 100 lines

How it starts

The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Objectif

Instructions à Exécuter

IMPORTANT : Exécute ce workflow étape par étape :

Gérer les git worktrees pour permettre le développement de plusieurs features en parallèle sans conflits.

Actions disponibles

create

Créer un nouveau worktree pour une feature.

Usage :

/dev:worktree create <feature-name> [base-branch]

Arguments :

  • feature-name : Nom de la feature (ex: "oauth-auth", "refactor-payment")
  • base-branch : Branche de base (défaut: main ou master)

Exemple :

/dev:worktree create oauth-auth
/dev:worktree create hotfix-payment main

Comportement :

  1. Détecter la branche principale (main/master)
  2. Normaliser le nom de la feature (kebab-case)
  3. Créer la branche feature/<feature-name> ou hotfix/<feature-name>
  4. Créer le worktree dans .worktrees/<feature-name>
  5. Mettre à jour .claude/data/.dev-worktrees.json avec les métadonnées
  6. Afficher les instructions pour basculer vers le worktree

list

Lister tous les worktrees actifs.

Usage :

/dev:worktree list

remove

Supprimer un worktree (après merge ou abandon).

Usage :

/dev:worktree remove <feature-name>

Comportement :

  1. Vérifier qu'il n'y a pas de modifications non commitées
  2. Demander confirmation si des commits non poussés existent
  3. Supprimer le worktree avec git worktree remove
  4. Optionnellement supprimer la branche (demander confirmation)
  5. Mettre à jour .claude/data/.dev-worktrees.json

status

Afficher le statut détaillé d'un ou tous les worktrees.

Usage :

/dev:worktree status [feature-name]

switch

Basculer vers un worktree existant (utilitaire de navigation).

Usage :

/dev:worktree switch <feature-name>

Comportement : Afficher les commandes pour changer de répertoire

Règles de nommage

  • Features : feature/<name> → worktree dans .worktrees/<name>
  • Hotfixes : hotfix/<name> → worktree dans .worktrees/<name>
  • Nom normalisé : kebab-case uniquement (convertir espaces et caractères spéciaux)

Read the full file on GitHub · 100 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. 12d ago First seen · 100 lines · 13 tokens per session scan A 14d60c704674

Subscribe to this mod's changes

dev:worktree is a skill published in the GitHub repository atournayre/claude-marketplace (9 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 620 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-31.

Git and workflow
Related

Other skills, from other repositories

prowler-commit

Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.

prowler-cloud/prowler · 33 tokens

gh-auth-isolation

Safely manage multiple GitHub identities (EMU + personal) in agent workflows.

github/gh-aw · 20 tokens

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.

rpamis/comet · 72 tokens

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.

zeenie-ai/OpenCompany · 51 tokens

changelog-composer

Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".

Mathews-Tom/armory · 67 tokens

re0-merge

Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…

LilMGenius/paperthin · 70 tokens