Borrowing it
Nothing to install: this file belongs to Kewton/CommandMate. 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/Kewton/CommandMate/main/.claude/commands/worktree-setup.mdgit clone --depth 1 https://github.com/Kewton/CommandMateWrote 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/kewton/commandmate/worktree-setup)<a href="https://agentmods.dev/commands/kewton/commandmate/worktree-setup"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/worktree-setup/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/kewton/commandmate/worktree-setup"><img src="https://agentmods.dev/badge/commands/kewton/commandmate/worktree-setup.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.00000 | $0.02467 |
| Opus 5.5 | $0.00000 | $0.00987 |
| Sonnet 5.5 | $0.00000 | $0.00493 |
| Haiku 4.5 | $0.00000 | $0.00247 |
Grade A, and why
worktree-setup scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST http://localhost:${CM_PORT:-3000}/api/repositories/sync How it starts
The opening of the file, as written. The whole thing — 285 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Setup スキル
概要
指定したIssue番号に対応するGit Worktree環境を自動構築するスキルです。
使用方法
/worktree-setup [Issue番号...]
例:
/worktree-setup 135
/worktree-setup 187 188 191 193
実行内容
あなたはWorktree環境セットアップの専門家です。以下の手順でWorktree環境を構築してください。 複数のIssue番号が指定された場合は、各Issueに対してPhase 1〜7を順番に繰り返し実行します。
パラメータ
- issue_numbers: 対象Issue番号(必須、1つ以上、スペース区切り、各番号は正の整数)
実行フェーズ
複数Issue指定時: 以下のPhase 1〜7を各Issueに対して順番に実行します。 ただし、Phase 2(前提条件チェック)は初回のみ実行し、Phase 6(Worktree同期)は全Issue完了後にまとめて1回実行します。
Phase 1: 入力検証
- Issue番号が正の整数であることを確認
- Issue番号が1〜2147483647の範囲内であることを確認
# 共通バリデーション関数を読み込み
# Synced with: src/cli/utils/input-validators.ts MAX_ISSUE_NO
source "$(dirname "$0")/../lib/validators.sh"
# Issue番号の検証
if ! validate_issue_no "$ISSUE_NO"; then
echo "Error: Invalid issue number"
exit 1
fi
Phase 2: 前提条件チェック
- 現在のディレクトリがGitリポジトリであることを確認
- developブランチが存在することを確認
- git worktreeコマンドが利用可能であることを確認
# Gitリポジトリチェック
git rev-parse --git-dir > /dev/null 2>&1 || { echo "Error: Not a git repository"; exit 1; }
# developブランチ存在チェック
git show-ref --verify --quiet refs/heads/develop || { echo "Error: develop branch not found"; exit 1; }
Phase 3: Worktree作成
- featureブランチ名を決定:
feature/{issue_number}-worktree - Worktreeディレクトリを決定:
../commandmate-issue-{issue_number} - git worktree addコマンドを実行
BRANCH_NAME="feature/${ISSUE_NO}-worktree"
WORKTREE_DIR="../commandmate-issue-${ISSUE_NO}"
# 既存Worktreeチェック
if git worktree list | grep -q "$WORKTREE_DIR"; then
echo "Worktree already exists: $WORKTREE_DIR"
else
# Worktree作成(developブランチから派生)
git worktree add -b "$BRANCH_NAME" "$WORKTREE_DIR" develop
fi
Phase 4: 環境設定
- Worktreeディレクトリに移動
- 依存関係インストール(必要な場合)
- Issue専用DBパスを設定
cd "$WORKTREE_DIR"
# 依存関係インストール(node_modulesがない場合)
# --include=dev: シェルが NODE_ENV=production だと vitest / eslint などが入らない
if [ ! -d "node_modules" ]; then
npm install --include=dev
fi
# .envファイルにIssue固有設定を追加(存在しない場合)
if [ ! -f ".env" ]; then
cp ~/.commandmate/.env .env 2>/dev/null || touch .env
fi
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 Changed · +1 lines 03766a48b8ce
- 1mo ago First seen · 284 lines · 0 tokens per session scan A 9ab0a2d6285f
worktree-setup is a command published in the GitHub repository Kewton/CommandMate (44 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,467 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
project
Manage projects: register repos, inspect, configure per-project settings, and remove.
pr-review
Intelligent PR code review with dynamic agent allocation based on change types.
afsr
Review feature spec - improve the spec itself before implementation (shortcut for feature-spec-review).
next
Suggest the most likely next workflow action based on current context.
reapply-patches
Reapply local modifications after a PBR update.
undo
Revert recent PBR-generated commits by phase/plan, safely using git revert.