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.
git clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/worktree-sync)<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/worktree-sync"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/worktree-sync/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/kumaran-is/claude-code-onboarding/worktree-sync"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/worktree-sync.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.00047 | $0.00567 |
| Opus 5 | $0.00023 | $0.00283 |
| Sonnet 5 | $0.00009 | $0.00113 |
| Haiku 4.5 | $0.00005 | $0.00057 |
Grade A, and why
worktree-sync 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 5d 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.
What it actually says
Worktree Sync
Create and maintain git worktrees so each open PR branch has its own directory on disk. No stashing. No context switching. Open multiple editor windows on different branches simultaneously.
Step 1 — Determine Mode
If $ARGUMENTS contains --new <branch-name>: skip to Step 3 (create one new branch + worktree).
Otherwise: run Step 2 (sync all open PRs).
Step 2 — Sync All Open PR Worktrees
# Verify GitHub CLI auth
gh auth status
# Create worktree base directory
mkdir -p ./tree
# Create a worktree for each open PR branch
gh pr list --json headRefName --jq '.[].headRefName' | while read branch; do
safe_name="${branch//\//-}"
branch_path="./tree/$safe_name"
if [ ! -d "$branch_path" ]; then
echo "Creating worktree: $branch → $branch_path"
git fetch origin "$branch" 2>/dev/null || true
git worktree add "$branch_path" "$branch"
else
echo "Already exists: $branch_path (skipping)"
fi
done
git worktree list
After sync: open each ./tree/<branch>/ in a separate terminal or editor window. Each directory is a full independent working copy sharing the same .git object store.
Step 3 — Create New Branch + Worktree
Use when starting a new feature branch and wanting an isolated working directory from day one.
# branch_name comes from --new argument (e.g. --new feature/auth)
branch_name="<extract branch name from $ARGUMENTS after --new>"
repo_root=$(git rev-parse --show-toplevel)
parent_dir=$(dirname "$repo_root")
safe_branch="${branch_name//\//-}"
worktree_path="$parent_dir/$(basename "$repo_root")-$safe_branch"
git worktree add -b "$branch_name" "$worktree_path"
echo "Worktree created at: $worktree_path"
echo "Open this directory in a separate editor window to work in parallel."
git worktree list
Step 4 — Prune Stale Worktrees
If a worktree directory was deleted manually, clean up the dangling reference:
git worktree prune
git worktree list
$ARGUMENTS
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.
- 5d ago First seen · 70 lines · 0 tokens per session scan A b466aaedf409
worktree-sync is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 567 once invoked, about $0.0002 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-09-03.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
handoff
Export a Waybill Bundle by default, or import one when requested.