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-deliver.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-deliver)<a href="https://agentmods.dev/commands/davila7/claude-code-templates/worktree-deliver"><img src="https://agentmods.dev/badge/commands/davila7/claude-code-templates/worktree-deliver/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-deliver"><img src="https://agentmods.dev/badge/commands/davila7/claude-code-templates/worktree-deliver.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.01000 |
| Opus 5.5 | $0.00005 | $0.00400 |
| Sonnet 5.5 | $0.00002 | $0.00200 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
worktree-deliver 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Deliver
Commit all work, push, and create a pull request from the current worktree.
Instructions
You are inside a worktree. Package up the work and deliver it as a PR.
Step 1: Validate Environment
- Verify this is a worktree (not the main working tree) using
git worktree list - Get current branch:
git branch --show-current - Verify branch follows
claude/*,claude-daniel/*, orreview/*pattern. If not, warn the user and ask if they want to continue. - Read
.worktree-task.mdif it exists to get the original task description
Step 2: Review Changes
- Run
git diff --statandgit diff --cached --statto show all changes - Run
git status --shortto show the full picture - If there are no changes at all (clean working tree, no commits ahead of main), inform the user there's nothing to deliver and stop.
Step 3: Clean Up Task File
Before staging anything, remove the worktree task file so it doesn't end up in the commit:
rm -f .worktree-task.md
Step 4: Confirm Files to Commit
Use AskUserQuestion to show the user what will be committed and ask for confirmation. List all modified, added, and untracked files.
Options:
- "Stage all changes" — stage everything
- "Let me choose" — user will specify which files to include
If the user wants to choose, ask them which files to stage.
Step 5: Stage and Commit
- Stage the confirmed files with
git add - Generate a commit message following conventional commits format
Commit Message Strategy:
-
Analyze the diff to determine the conventional commit type:
feat:— New functionality, new files, new exports, new API endpointsfix:— Bug fixes, error corrections, fixing broken behaviorrefactor:— Code restructuring without changing behaviordocs:— Documentation only changestest:— Adding or modifying testschore:— Build scripts, configs, maintenance tasks
-
Generate a commit message based on:
- The task description from
.worktree-task.md(if it was found) - A brief summary of what the diff actually changed
- Format:
<type>: <subject>(max 72 characters)
- The task description from
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 · 128 lines · 12 tokens per session scan A ec3a16c296b8
worktree-deliver is a command published in the GitHub repository davila7/claude-code-templates (32,670 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 1,000 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-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-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.
ccc-skill-create
Analyze the repository's git history for commit conventions, co-changing files, workflows and test patterns, and generate a SKILL.md (and optional instincts) that teaches them. Use when you want your team's practices captured as a project skill.
ccc-checkpoint
Create, verify, list or clear named workflow checkpoints: a verified git snapshot logged with its SHA, compared later for changed files, tests and build. Use before risky steps and at feature milestones.
caveman-commit
Generate a terse caveman-style commit message for staged changes.