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.
git clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/rules/digi-uw/openelis-global-2/git-worktree-parallel-work)<a href="https://agentmods.dev/rules/digi-uw/openelis-global-2/git-worktree-parallel-work"><img src="https://agentmods.dev/badge/rules/digi-uw/openelis-global-2/git-worktree-parallel-work/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/rules/digi-uw/openelis-global-2/git-worktree-parallel-work"><img src="https://agentmods.dev/badge/rules/digi-uw/openelis-global-2/git-worktree-parallel-work.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.00428 | $0.00428 |
| Opus 5.5 | $0.00171 | $0.00171 |
| Sonnet 5.5 | $0.00086 | $0.00086 |
| Haiku 4.5 | $0.00043 | $0.00043 |
Grade A, and why
git-worktree-parallel-work 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
Git worktrees — parallel work discipline
This repo uses multiple worktrees for parallel work. The Cursor workspace root may not be the tree where the current task’s branch is checked out.
Non‑negotiables
-
Task = directory first
Beforegitcommands, Playwright, Maven, or editing “the” branch for a ticket/PR, confirm which worktree path owns that branch (git worktree list). -
Never fight the lock
If branchBis already checked out in worktreeW, do notgit checkout Bin another clone. UseW(cd/ absolute paths / open folder)—never createlocal/*(or other) duplicate branches on the main repo just to unblock checkout. -
Shells and tests follow the tree
Prefix commands:cd <worktree-root> && …for that task. Do not assumeWorkspace Pathis the PR tree when parallel work exists. -
One line of work = one branch ref
PRs track one remote branch (e.g.followup/e2e-runtime-remediation). All commits for that PR must land on that ref’s checkout—not a straylocal/…branch on another path. -
If unsure
Rungit worktree list, identify the row whereBis checked out, and operate only under that path until the user changes scope.
Anti‑patterns
- Checking out the same branch in two directories.
- “Sync branches” via inventing
local/<name>on the main clone while the real branch lives in~/.cursor/worktrees/.... - Running Playwright or CI‑critical commands from the wrong worktree and then debugging “mystery” drift.
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 · 32 lines · 428 tokens per session scan A e81f8e6bb647
git-worktree-parallel-work is a cursor rule published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (273 stars, last pushed yesterday), licensed MPL-2.0. It adds 428 tokens to every session, about $0.0017 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 cursor rules, from other repositories
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.
git-workflow
Git commit format and PR process - conventional commits.
branching-merging-strategy
This is a set of instructions to the AI Assistant for branching and merging strategy.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.