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 agentmods add commands/thedecipherist/claude-code-mastery-project-starter-kit/worktreegit clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kitWhat 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 | $0.00011 | $0.00973 |
| Opus 5 | $0.00005 | $0.00487 |
| Sonnet 5 | $0.00002 | $0.00195 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
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 3d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree — Isolated Task Branch
Create a new git worktree so this task runs on its own branch in its own directory. Main stays untouched. If anything goes wrong, delete the branch — zero risk.
Arguments: $ARGUMENTS
Step 0 — Parse Arguments
- First argument: branch name (required). If not provided, ASK the user.
- Second argument: base branch to branch from (optional, defaults to
mainormaster)
Branch naming convention: task/<descriptive-name>
- If the user provides just a name like
auth-fix, prefix it:task/auth-fix - If they already include a prefix like
feat/login, use as-is
Step 1 — Verify Git State
Before creating anything, verify:
# Must be in a git repo
git rev-parse --git-dir
# Check for uncommitted changes on current branch
git status --porcelain
If there are uncommitted changes: WARN the user. Ask if they want to:
- Stash changes first (
git stash) - Commit changes first
- Abort
NEVER create a worktree with dirty state — changes could bleed between worktrees.
Step 2 — Determine Base Branch
# Find the default branch (main or master)
git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@'
If no remote, fall back to checking if main or master exists locally.
Use the second argument if provided, otherwise use the detected default branch.
Step 3 — Create Branch + Worktree
The worktree directory goes next to the current repo as ../<repo-name>--<branch-name>:
# Example: if repo is at ~/projects/my-app and branch is task/auth-fix
# Worktree goes to ~/projects/my-app--task-auth-fix
REPO_NAME=$(basename "$(git rev-parse --show-toplevel)")
BRANCH_NAME="$1"
WORKTREE_DIR="../${REPO_NAME}--${BRANCH_NAME//\//-}"
# Create the branch and worktree in one step
git worktree add -b "$BRANCH_NAME" "$WORKTREE_DIR" "$BASE_BRANCH"
Step 4 — Verify
# List all worktrees to confirm
git worktree list
Step 5 — Report
Output a summary:
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.
- 3d ago First seen · 125 lines · 11 tokens per session scan A 51c969a536db
worktree is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 11 tokens to every session and 973 once invoked, about $0.0001 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-08-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.