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 winstonkoh87/Athena-Public --skill git-worktree-swarmgit clone --depth 1 https://github.com/winstonkoh87/Athena-PublicWrote 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/winstonkoh87/athena-public/git-worktree-swarm)<a href="https://agentmods.dev/skills/winstonkoh87/athena-public/git-worktree-swarm"><img src="https://agentmods.dev/badge/skills/winstonkoh87/athena-public/git-worktree-swarm/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/winstonkoh87/athena-public/git-worktree-swarm"><img src="https://agentmods.dev/badge/skills/winstonkoh87/athena-public/git-worktree-swarm.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.00027 | $0.00685 |
| Opus 5 | $0.00014 | $0.00342 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00003 | $0.00068 |
Grade A, and why
git-worktree-swarm 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Worktree Swarm Orchestrator
Sets up parallel, isolated git environments so multiple sub-agents can work on the same repository simultaneously without merge conflicts. Uses wave-based execution to respect task dependencies.
Triggers
"swarm", "parallel agents", "setup worktrees", "multi-agent", "wave execution"
Core Mechanics
Phase 1: Setup
- Detect current branch.
- Spawn
ntemporary worktrees (.agent-workspace-1, etc.). - Assign tasks to isolated clones.
Phase 2: Wave Execution (Dependency DAG)
Plans are grouped into waves based on dependency analysis:
WAVE 1 (parallel — no dependencies)
├── Worktree A: Task 1 (User model) → Fresh context (P513)
├── Worktree B: Task 2 (Product model) → Fresh context (P513)
│
[State merge: A.state + B.state → combined handoff]
│
WAVE 2 (parallel — depends on Wave 1)
├── Worktree C: Task 3 (Orders API, needs User model)
├── Worktree D: Task 4 (Cart API, needs Product model)
│
[State merge: C.state + D.state → combined handoff]
│
WAVE 3 (sequential — depends on Wave 2)
└── Worktree E: Task 5 (Checkout UI, needs Orders + Cart)
Wave Assignment Rules:
| Condition | Assignment |
|---|---|
| Task has no dependencies | Wave 1 |
| Task depends on Wave N output | Wave N+1 |
| Tasks touch the same files | Same wave, sequential (not parallel) |
| Task has cross-cutting concerns | Latest wave of any dependency |
Phase 3: Context Isolation (P513)
Each worktree agent receives only:
- The specific plan/task
- Relevant source files (from dependency analysis)
- STATE.md (accumulated decisions from prior waves)
- Project context (design.md / REQUIREMENTS.md)
Never: full conversation history, debug logs, unrelated research.
Phase 4: Merge
- Each task commits atomically (P43 micro-commit).
- Merge worktrees back to main branch in wave order.
- Conflict resolution: if merge conflicts arise, spawn resolution agent.
- Cleanup: remove temporary worktrees.
Reference Paths
- Protocol 513: Context Isolation
- Protocol 43: Micro-Commit
.context/memories/protocols/engineering/100-git-worktree-parallelism.md.context/memories/protocols/architecture/409-parallel-worktree-orchestration.md
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.
- 10d ago First seen · 82 lines · 27 tokens per session scan A bd6a5f958bec
git-worktree-swarm is a skill published in the GitHub repository winstonkoh87/Athena-Public (587 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 685 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-08-30.
Other skills, from other repositories
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
Release Notes Generator
Generate professional software release notes from a commit log: classify changes, write user-facing summaries, draft a publishable announcement, and assess release readiness. Use for release, changelog, version, and deploy requests.
pinned-release-checklist
Minimal guidance-only Skill used by release-pinned compatibility examples.
Release Readiness Reviewer
Reviews a release candidate and produces a go/no-go readiness decision.
Release Checklist
Check release readiness and record a release note. Use for release and rollback requests.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.