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/rtk-ai/rtk/worktreegit clone --depth 1 https://github.com/rtk-ai/rtkWhat 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.00007 | $0.01434 |
| Opus 5 | $0.00003 | $0.00717 |
| Sonnet 5 | $0.00001 | $0.00287 |
| Haiku 4.5 | $0.00001 | $0.00143 |
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 2d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Setup
Create isolated git worktrees with instant feedback and background Cargo check.
Performance: ~1s setup + background cargo check
Usage
/tech:worktree feature/new-filter # Creates worktree + background cargo check
/tech:worktree fix/typo --fast # Skip cargo check (instant)
/tech:worktree feature/perf --no-check # Skip cargo check
Behavior: Creates the worktree and displays the path. Navigate manually with cd .worktrees/{branch-name}.
⚠️ Important - Claude Context: If Claude Code is currently running, restart it in the new worktree:
/exit # Exit current Claude session
cd .worktrees/fix-bug-name # Navigate to worktree
claude # Start Claude in worktree context
Check cargo check status: /tech:worktree-status feature/new-filter
Branch Naming Convention
Always use Git branch naming with slashes:
- ✅
feature/new-filter→ Branch:feature/new-filter, Directory:.worktrees/feature-new-filter - ✅
fix/bug-name→ Branch:fix/bug-name, Directory:.worktrees/fix-bug-name - ❌
feature-new-filter→ Wrong: Missing category prefix
Implementation
Execute this single bash script with branch name from $ARGUMENTS:
#!/bin/bash
set -euo pipefail
trap 'kill $(jobs -p) 2>/dev/null || true' EXIT
# Validate git repository - always use main repo root (not worktree root)
GIT_COMMON_DIR="$(git rev-parse --git-common-dir 2>/dev/null)"
if [ -z "$GIT_COMMON_DIR" ]; then
echo "❌ Not in a git repository"
exit 1
fi
REPO_ROOT="$(cd "$GIT_COMMON_DIR/.." && pwd)"
# Parse flags
RAW_ARGS="$ARGUMENTS"
BRANCH_NAME="$RAW_ARGS"
SKIP_CHECK=false
if [[ "$RAW_ARGS" == *"--fast"* ]]; then
SKIP_CHECK=true
BRANCH_NAME="${BRANCH_NAME// --fast/}"
fi
if [[ "$RAW_ARGS" == *"--no-check"* ]]; then
SKIP_CHECK=true
BRANCH_NAME="${BRANCH_NAME// --no-check/}"
fi
# Validate branch name
if [[ "$BRANCH_NAME" =~ [[:space:]\$\`] ]]; then
echo "❌ Invalid branch name (spaces or special characters not allowed)"
exit 1
fi
if [[ "$BRANCH_NAME" =~ [~^:?*\\\[\]] ]]; then
echo "❌ Invalid branch name (git forbidden characters: ~ ^ : ? * [ ])"
exit 1
fi
# Paths - sanitize slashes to avoid nested directories
WORKTREE_NAME="${BRANCH_NAME//\//-}"
WORKTREE_DIR="$REPO_ROOT/.worktrees/$WORKTREE_NAME"
LOG_FILE="/tmp/worktree-cargo-check-${WORKTREE_NAME}.log"
# 1. Check .gitignore (fail-fast)
if ! grep -qE "^\.worktrees/?$" "$REPO_ROOT/.gitignore" 2>/dev/null; then
echo "❌ .worktrees/ not in .gitignore"
echo "Run: echo '.worktrees/' >> .gitignore && git add .gitignore && git commit -m 'chore: ignore worktrees'"
exit 1
fi
# 2. Create worktree (fail-fast)
echo "Creating worktree for $BRANCH_NAME..."
mkdir -p "$REPO_ROOT/.worktrees"
if ! git worktree add "$WORKTREE_DIR" -b "$BRANCH_NAME" 2>/tmp/worktree-error.log; then
echo "❌ Failed to create worktree"
cat /tmp/worktree-error.log
exit 1
fi
# 3. Background cargo check (unless --fast / --no-check)
if [ "$SKIP_CHECK" = false ] && [ -f "$WORKTREE_DIR/Cargo.toml" ]; then
(
cd "$WORKTREE_DIR"
echo "⏳ Cargo check started at $(date +%H:%M:%S)" > "$LOG_FILE"
if cargo check --all-targets >> "$LOG_FILE" 2>&1; then
echo "✅ Cargo check passed at $(date +%H:%M:%S)" >> "$LOG_FILE"
else
echo "❌ Cargo check failed at $(date +%H:%M:%S)" >> "$LOG_FILE"
fi
) &
CHECK_RUNNING=true
else
CHECK_RUNNING=false
fi
# 4. Report (instant feedback)
echo ""
echo "✅ Worktree ready: $WORKTREE_DIR"
if [ "$CHECK_RUNNING" = true ]; then
echo "⏳ Cargo check running in background..."
echo "📝 Check status: /tech:worktree-status $BRANCH_NAME"
echo "📝 Or view log: cat $LOG_FILE"
elif [ "$SKIP_CHECK" = true ]; then
echo "⚡ Cargo check skipped (--fast / --no-check mode)"
fi
echo ""
echo "🚀 Next steps:"
echo ""
echo "If Claude Code is running:"
echo " 1. /exit"
echo " 2. cd $WORKTREE_DIR"
echo " 3. claude"
echo ""
echo "If Claude Code is NOT running:"
echo " cd $WORKTREE_DIR && claude"
echo ""
echo "✅ Ready to work!"
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.
- 2d ago First seen · 189 lines · 7 tokens per session scan A a0021c64d67f
worktree is a command published in the GitHub repository rtk-ai/rtk (78,131 stars, last pushed today), licensed Apache-2.0. It adds 7 tokens to every session and 1,434 once invoked, about $0.0000 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
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
worktree
Create a git worktree for isolated feature/fix work.
sync
Check guide/landing synchronization status.
version
Display current guide and Claude Code versions.