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 J-StaR-Films-Studios/VibeCode-Protocol-Suite --skill git-worktreegit clone --depth 1 https://github.com/J-StaR-Films-Studios/VibeCode-Protocol-SuiteWrote 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/j-star-films-studios/vibecode-protocol-suite/git-worktree)<a href="https://agentmods.dev/skills/j-star-films-studios/vibecode-protocol-suite/git-worktree"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/git-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/j-star-films-studios/vibecode-protocol-suite/git-worktree"><img src="https://agentmods.dev/badge/skills/j-star-films-studios/vibecode-protocol-suite/git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 41 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.00023 | $0.00434 |
| Opus 5 | $0.00012 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
git-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 7d 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 Worktree Skill
Manage parallel development environments without manual path juggling.
When to Use
- Setting up parallel agents
- Multi-agent development
- When "worktree" is mentioned
- Need isolated environments for different features
Status Check
git worktree list
git branch --list
Actions
[NEW] Create Agent Environment
-
Name the Agent: Short identifier (e.g.,
frontend-refactor,agent-3) -
Define Paths:
- Branch:
[agent-name] - Folder:
../[repo-name]-[agent-name]
- Branch:
-
Execute:
git branch [branch_name]
git worktree add [folder_path] [branch_name]
-
Validate:
git worktree list -
Context Migration (ask user):
cp .env [worktree_path]/.env
# If SQLite:
mkdir -p [worktree_path]/prisma
cp prisma/dev.db [worktree_path]/prisma/dev.db
- Initialize:
pnpm installin new worktree
[SYNC] Synchronize Agents
- Ask: Sync ALL or SPECIFIC worktree?
- Execute:
git fetch origin
cd [worktree_path]
git merge origin/main # or rebase
cd -
[KILL] Teardown Agent
- Select worktree from list
- Execute:
git worktree remove [worktree_path]
git branch -d [branch_name] # Ask before deleting!
git worktree prune
Troubleshooting
- "already checked out": Use a new branch name
- Stale entries: Run
git worktree prune - Files still tracked: Directory was deleted manually—prune first
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.
- 7d ago First seen · 79 lines · 23 tokens per session scan A 1b6dd6d8619e
git-worktree is a skill published in the GitHub repository J-StaR-Films-Studios/VibeCode-Protocol-Suite (24 stars, last pushed today), licensed ISC. It adds 23 tokens to every session and 434 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
git-workflow
A guide for handling Git repository work safely, including status checks, branches, commits, pushes, pull requests, and rebasing. Git is a version-control system that records code changes and coordinates work between developers.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
setup-pre-commit
A setup guide for Git pre-commit checks, which run automatically before a commit is created. It configures Husky, lint-staged, Prettier, type checking, and tests in a repository.
resolving-merge-conflicts
A procedure for resolving conflicts during an active Git merge or rebase. It traces the purpose of both changes, resolves each conflict, runs the project's checks, and completes the operation.
git-guardrails-claude-code
A Claude Code hook that blocks selected dangerous Git commands before they run. It can be installed for one project or for all projects.
pr-stack
Plan and execute splitting a large PR or branch into a reviewable stacked PR sequence.