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/nwiizo/ccswarmnpx agentmods add skills/nwiizo/ccswarm/git-worktreeWrote 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/nwiizo/ccswarm/git-worktree)<a href="https://agentmods.dev/skills/nwiizo/ccswarm/git-worktree"><img src="https://agentmods.dev/badge/skills/nwiizo/ccswarm/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/nwiizo/ccswarm/git-worktree"><img src="https://agentmods.dev/badge/skills/nwiizo/ccswarm/git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.00305 |
| Opus 5.5 | $0.00010 | $0.00122 |
| Sonnet 5.5 | $0.00005 | $0.00061 |
| Haiku 4.5 | $0.00002 | $0.00030 |
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 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
Multi-step workflow for parallel development using git worktrees.
Create Worktree
# Feature worktree
git worktree add ../ccswarm-feature-$ARGUMENTS feature/$ARGUMENTS
# Bug fix worktree
git worktree add ../ccswarm-bugfix-$ARGUMENTS hotfix/$ARGUMENTS
Agent Team Integration
With Agent Teams, each agent automatically gets isolation: worktree. For manual worktree setup:
git worktree add ../ccswarm-frontend feature/ui-redesign # Frontend agent
git worktree add ../ccswarm-backend feature/api-enhancement # Backend agent
git worktree add ../ccswarm-devops feature/ci-cd-improvement # DevOps agent
Management
git worktree list # List all worktrees
git worktree remove ../ccswarm-feature-$ARGUMENTS # Remove after merge
git worktree prune # Clean stale entries
Best Practices
- One worktree per feature/bug
- Naming:
ccswarm-<type>-<description> - Clean up after merging
- Run
git worktree pruneperiodically
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 · 44 lines · 24 tokens per session scan A 438458926921
git-worktree is a skill published in the GitHub repository nwiizo/ccswarm (153 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 305 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-08-30.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
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.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…