Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Insajin/autopus-adknpx agentmods add skills/insajin/autopus-adk/git-worktreesWrote 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/insajin/autopus-adk/git-worktrees)<a href="https://agentmods.dev/skills/insajin/autopus-adk/git-worktrees"><img src="https://agentmods.dev/badge/skills/insajin/autopus-adk/git-worktrees.svg" alt="Measured on agentmods" 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.00018 | $0.00588 |
| Opus 5 | $0.00009 | $0.00294 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
git-worktrees 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.
What it actually says
Git Worktrees Skill
Git Worktree를 사용하여 여러 브랜치를 동시에 작업하는 스킬입니다.
Git Worktree 기본
# 새 worktree 생성 (브랜치 자동 생성)
git worktree add ../project-feature feature/new-feature
# 기존 브랜치로 worktree 생성
git worktree add ../project-hotfix hotfix/critical-fix
# worktree 목록 확인
git worktree list
# worktree 제거
git worktree remove ../project-feature
git worktree prune # 정리
에이전트 격리 패턴
코딩 에이전트의 병렬 작업을 격리할 때:
# 에이전트별 독립 worktree 생성
git worktree add /tmp/agent-backend-work agent/backend-$(date +%s)
git worktree add /tmp/agent-frontend-work agent/frontend-$(date +%s)
git worktree add /tmp/agent-tester-work agent/tester-$(date +%s)
각 에이전트는 자신의 worktree에서:
- 독립적으로 파일 수정
- 파일 충돌 없이 병렬 실행
- 완료 후 메인 브랜치에 머지
Worktree 워크플로우
기능 개발 + 핫픽스 동시 진행
# 현재 기능 개발 중
git worktree add ../hotfix hotfix/security-patch
# 핫픽스 worktree에서 작업
cd ../hotfix
# 수정...
git commit -m "fix(security): XSS 취약점 수정"
git push origin hotfix/security-patch
# 원래 작업으로 복귀
cd ../main-project
코드 리뷰 동시 진행
# PR 브랜치를 worktree로 체크아웃
git worktree add ../review-pr-123 pr-review/123
git fetch origin pull/123/head:pr-review/123
주의 사항
- 같은 브랜치를 두 개의 worktree에서 사용 불가
.git/디렉토리는 공유됨 (커밋, 스테이지 독립)- Worktree 경로에 공백 사용 피할 것
- 에이전트 작업 완료 후 반드시 제거
정리 스크립트
#!/bin/sh
# 오래된 에이전트 worktree 정리
git worktree list --porcelain | \
grep "^worktree " | \
grep "/tmp/agent-" | \
awk '{print $2}' | \
xargs -I{} git worktree remove {}
git worktree prune
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 · 87 lines · 18 tokens per session scan A 26d3f6df2865
git-worktrees is a skill published in the GitHub repository Insajin/autopus-adk (109 stars, last pushed today), licensed MIT. It adds 18 tokens to every session and 588 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-09-03.
Other skills, from other repositories
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
deploy-local
End-to-end local deployment loop for Gitea-hosted projects. Use when the user wants to commit on dev, push to remote, monitor the golden CI/build/deploy workflow, validate prod on the configured prod host, and fix lint/test/pipeline failures until deployment is healthy.
github-issues
Create well-structured GitHub issues with proper labels, descriptions, and acceptance criteria. Use when creating bug reports, feature requests, or tracking tasks.
git-commit
Create well-structured conventional commit messages following Conventional Commits standard. Use when committing changes, preparing PRs, or generating changelogs.
using-git-worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification.
changelog-generator
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.