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 skills add brain-bootstrap/claude-code-brain-bootstrap --skill worktree-statusgit clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapWrote 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/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree-status)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree-status"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree-status/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/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree-status"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree-status.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.00036 | $0.00585 |
| Opus 5.5 | $0.00014 | $0.00234 |
| Sonnet 5.5 | $0.00007 | $0.00117 |
| Haiku 4.5 | $0.00004 | $0.00059 |
Grade A, and why
worktree-status 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.
What it actually says
Worktree Status Skill
Show all active git worktrees with their branch, dirty/clean status, and last commit.
Usage
/worktree-status # Show all worktrees
/worktree-status verbose # Include last 3 commits per worktree
Implementation
Execute this script:
#!/bin/bash
set -euo pipefail
VERBOSE=false
if [[ "${ARGUMENTS:-}" == *"verbose"* ]]; then
VERBOSE=true
fi
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
echo "Git Worktrees"
echo "============="
echo ""
COUNT=0
while IFS= read -r line; do
if [[ "$line" =~ ^([^[:space:]]+)[[:space:]]+([0-9a-f]+)[[:space:]]+\[(.+)\]$ ]]; then
WT_PATH="${BASH_REMATCH[1]}"
WT_COMMIT="${BASH_REMATCH[2]}"
WT_BRANCH="${BASH_REMATCH[3]}"
if git -C "$WT_PATH" diff --quiet 2>/dev/null && git -C "$WT_PATH" diff --cached --quiet 2>/dev/null; then
STATUS="clean"
else
CHANGED=$(git -C "$WT_PATH" status --short 2>/dev/null | wc -l | xargs)
STATUS="dirty ($CHANGED files)"
fi
SHORT_HASH="${WT_COMMIT:0:7}"
echo " Branch: $WT_BRANCH"
echo " Path: $WT_PATH"
echo " Status: $STATUS"
echo " Commit: $SHORT_HASH"
if [ "$VERBOSE" = true ]; then
echo " Recent commits:"
git --no-pager -C "$WT_PATH" log --oneline -3 2>/dev/null | sed 's/^/ /' || true
fi
echo ""
COUNT=$((COUNT + 1))
fi
done < <(git worktree list 2>/dev/null)
echo "Total: $COUNT worktree(s)"
echo ""
echo "Create: \/worktree <branch>"
echo "Cleanup: \/clean-worktrees"
Integration
Related skills:
/worktree— create/manage worktrees/clean-worktrees— remove merged worktrees
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 · 82 lines · 36 tokens per session scan A 6614626e4bda
worktree-status is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 36 tokens to every session and 585 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
review-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
merge-docs
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.