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 bostonaholic/team --skill team-worktreegit clone --depth 1 https://github.com/bostonaholic/teamWrote 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/bostonaholic/team/team-worktree)<a href="https://agentmods.dev/skills/bostonaholic/team/team-worktree"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-worktree/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/bostonaholic/team/team-worktree"><img src="https://agentmods.dev/badge/skills/bostonaholic/team/team-worktree.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.00025 | $0.00334 |
| Opus 5.5 | $0.00010 | $0.00134 |
| Sonnet 5.5 | $0.00005 | $0.00067 |
| Haiku 4.5 | $0.00003 | $0.00033 |
Grade A, and why
team-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 8d 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
Team Worktree
Before finalizing prose you author, read the writing standards.
Create one isolated git worktree per involved repo, all on branch <id>, without touching any main working tree: the home repo in single-repo mode (default), or every repo in docs/plans/<id>/4-repos.md when it exists.
Core contracts
- Detect a linked checkout with
git rev-parse --git-dirandgit rev-parse --git-common-dir. - Non-default branch in an existing linked checkout → skip worktree creation for this repo.
- Default branch → report and stop.
- Single-repo:
git worktree add .claude/worktrees/<branch>. Each4-repos.mdentry:git -C <repo> worktree add .claude/worktrees/<branch>. - Record every created path under
## Worktreesin4-repos.md.
Procedure references
Read each reference completely when reaching it, in order; later stages depend on earlier state and gates.
What ships with it
12 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- agents/openai.yaml 175 B
- playbooks/provisioned-teardown.md 3.5 KB
- playbooks/worktree.md 5.1 KB
- references/01-input.md 715 B
- references/02-detect-mode.md 297 B
- references/03-detect-existing-worktree.md 1.0 KB
- references/04-execution.md 3.2 KB
- scripts/add-worktree.sh 2.9 KB runs code
- scripts/detect-worktree.sh 2.1 KB runs code
- scripts/run-teardown.sh 4.7 KB runs code
- scripts/sweep-residue.sh 1.9 KB runs code
- scripts/sweep-worktrees.sh 11 KB runs code
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.
- 8d ago Changed · -4 lines 53b515f09f2c
- 1mo ago Changed · -1 lines 5fb0086c9167
- 1mo ago Changed · -18 tokens per session 9345aa78e601
- 1mo ago Changed · -1 lines 4db27f4dcbbe
- 1mo ago Changed · +3 lines 427342a0c6f5
- 1mo ago Changed · -228 lines · -56 tokens per session 2c9996a0130b
- 1mo ago First seen · 261 lines · 99 tokens per session scan A df1974454eae
team-worktree is a skill published in the GitHub repository bostonaholic/team (11 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 334 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
git-integration
Git commit patterns, formats, and conventions for GSD methodology. Provides atomic commits per task, structured commit messages, planning file commits, branch management, and milestone tag operations.
audit-trail
Full traceability from PRD to code commit through the CCPM spec-driven pipeline.
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
issue-tracking
Track beads as git-backed issues with persistent attribution, supporting Gas Town's bead lifecycle and convoy progress monitoring.