Claude Code Templates is a command-line tool and catalogue for configuring Anthropic’s Claude Code with agents, commands, settings, hooks, integrations, skills, and project templates. Developers use it to browse and install reusable components for their coding workflows. The catalogue includes many of these Claude Code components.
Borrowing it
Nothing to install: this file belongs to davila7/claude-code-templates. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/davila7/claude-code-templates/main/.claude/commands/worktree-init.mdgit clone --depth 1 https://github.com/davila7/claude-code-templatesWrote 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/commands/davila7/claude-code-templates/worktree-init)<a href="https://agentmods.dev/commands/davila7/claude-code-templates/worktree-init"><img src="https://agentmods.dev/badge/commands/davila7/claude-code-templates/worktree-init/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/commands/davila7/claude-code-templates/worktree-init"><img src="https://agentmods.dev/badge/commands/davila7/claude-code-templates/worktree-init.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.00012 | $0.00831 |
| Opus 5.5 | $0.00005 | $0.00332 |
| Sonnet 5.5 | $0.00002 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
worktree-init 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 1mo 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Parallel Init
Create multiple git worktrees for parallel development: $ARGUMENTS
Instructions
You are setting up parallel worktrees so the user can work on multiple tasks simultaneously in separate Ghostty terminal panels, each running its own Claude instance.
Step 1: Validate Environment
- Check this is a git repository:
git rev-parse --is-inside-work-tree - Get the repo name:
basename $(git rev-parse --show-toplevel) - Get the main branch name (check for
mainormaster):git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'— if that fails, default tomain - Ensure working tree is clean:
git status --porcelain. If dirty, warn the user and ask if they want to continue. - Fetch latest:
git fetch origin
Step 2: Parse Tasks
Parse tasks from $ARGUMENTS. Tasks are separated by | (pipe character).
If $ARGUMENTS is empty, use AskUserQuestion to ask the user to describe their tasks (they can provide multiple separated by |).
For each task description:
- Trim whitespace
- Generate a kebab-case branch name:
claude/<kebab-case-task>(max 50 chars, alphanumeric and hyphens only) - Generate a worktree directory path:
../worktrees/<repo-name>/claude-<kebab-case-task>
Step 3: Create Worktrees
For each task:
- Create the parent directory if needed:
mkdir -p ../worktrees/<repo-name> - Create the worktree:
git worktree add -b claude/<name> ../worktrees/<repo-name>/claude-<name> origin/<main-branch> - Write a
.worktree-task.mdfile inside the new worktree with this content:# Worktree Task **Branch:** claude/<name> **Task:** <original task description> **Created:** <ISO date> **Source repo:** <path to main repo>
Step 4: Check for Dependencies
If a package.json exists in the repo root, note that each worktree may need npm install (or the appropriate package manager).
Check for:
package-lock.json→ npm installyarn.lock→ yarn installpnpm-lock.yaml→ pnpm installbun.lockb→ bun install
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.
- 1mo ago First seen · 89 lines · 12 tokens per session scan A 32a29d3468a2
worktree-init is a command published in the GitHub repository davila7/claude-code-templates (32,814 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 831 once invoked, about $0.0000 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-08-30.
Other commands, from other repositories
ccc-fork
Fork the current work into isolated git worktrees to try several approaches side by side, compare them on measured results, and merge the winner. Use when choosing between implementations, attempting a risky refactor, or testing competing bug theories.
ccc-multi-repo
Coordinate one change across several repositories in a single session with --add-dir: shared branch names, linked PRs, dependency-ordered merges and per-repo verification. Use for API contract changes, shared library updates and cross-service refactors.
ccc-parallel
Run several Claude Code agents at once, each in its own git worktree and branch, then merge the results through one coordinator. Use when you have independent tasks to develop concurrently.
ccc-ao
Spawn, monitor, stop and merge parallel agents in isolated git worktrees through the Composio ao CLI. Use when you want several agents working on one project at once.
ccc-pr
Open a pull request for the current branch: commit pending work, run tests, push, and create the PR with gh. Use when a branch is ready for review.
ccc-verify
Verify the current codebase in a fixed order (build, types, lint, tests with coverage, secrets, debug logs, git status) and return a PASS/FAIL report with a ready-for-PR verdict. Use before committing, before opening a PR, or when asked to check that everything still works.