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 joaquimscosta/arkhe-claude-plugins --skill creating-worktreegit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/creating-worktree)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/creating-worktree"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-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/joaquimscosta/arkhe-claude-plugins/creating-worktree"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/creating-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.00078 | $0.01773 |
| Opus 5.5 | $0.00031 | $0.00709 |
| Sonnet 5.5 | $0.00016 | $0.00355 |
| Haiku 4.5 | $0.00008 | $0.00177 |
Grade A, and why
creating-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 yesterday.
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 — 203 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Creation Workflow
Create isolated git worktrees in .claude/worktrees/ with intelligent branch naming. Combines worktree isolation with the same naming convention as the creating-branch skill.
Usage
This skill is invoked when:
- User runs
/worktreeor/git:worktreecommand - User requests to create a worktree for isolated work
Two Operation Modes
Mode 1: With Description (Manual)
The command takes a description and automatically detects the commit type.
Format: /worktree <description>
Examples:
/worktree add user authentication
# Worktree: .claude/worktrees/user-authentication
# Branch: feat/001-user-authentication
/worktree fix login bug
# Worktree: .claude/worktrees/login-bug
# Branch: fix/002-login-bug
/worktree refactor auth service
# Worktree: .claude/worktrees/auth-service
# Branch: refactor/003-auth-service
Mode 2: Auto-Generate from Changes (No Arguments)
When no arguments provided and no sdlc-develop specs exist, analyze uncommitted changes to generate names automatically.
Format: /worktree (no arguments)
Process:
- Check for sdlc-develop specs (see Mode 3)
- If no specs, check for uncommitted changes (both staged and unstaged)
- If no changes exist, display error and require description
- If changes exist, analyze to generate description
- Create worktree with auto-generated names
Mode 3: From SDLC-Develop Spec (Arkhe Integration)
When no arguments provided and sdlc-develop specs exist, create worktree linked to an existing feature spec.
Detection Flow:
- Check if
.arkhe.yamlexists -> readdevelop.specs_dir(default:arkhe/specs) - Scan
{specs_dir}/for existing spec directories - If specs found -> present selection via
AskUserQuestion - Use spec directory name for worktree and branch names
Naming Convention
This skill produces dual names:
| Component | Format | Example |
|---|---|---|
| Worktree directory | .claude/worktrees/{keywords} |
.claude/worktrees/user-authentication |
| Git branch | {type}/{number}-{keywords} |
feat/001-user-authentication |
What ships with it
3 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.
- yesterday First seen · 203 lines · 78 tokens per session scan A 1322d6531c69
creating-worktree is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,773 once invoked, about $0.0003 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-16.
Other skills, from other repositories
git-workflow
Git branching, commits, and PR workflow following GitFlow conventions.
pr-creator
Create well-structured pull requests with proper descriptions and labels.
diff-project
Shows what changed in dotforge since the project's last sync, to decide whether running /forge sync is worthwhile.
finish
Ship phase — merge, PR, keep, or discard with pre-merge verification.
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-rc
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.