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 agentmods add rules/alphabitcore/nexus-gateway/worktree-per-sessiongit clone --depth 1 https://github.com/AlphaBitCore/nexus-gatewayWhat 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 | $0.00378 | $0.00378 |
| Opus 5 | $0.00189 | $0.00189 |
| Sonnet 5 | $0.00076 | $0.00076 |
| Haiku 4.5 | $0.00038 | $0.00038 |
Grade A, and why
worktree-per-session 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 2d 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
Worktree per session (binding)
Each parallel Claude Code / Cursor session runs in its own git worktree so working tree, index, and .git/index.lock are private to that session.
Conventions
- Spawn:
git worktree add ./worktrees/<topic> [-b feature/<new-branch>] [<base>]../worktrees/is gitignored. - Clean up after merge:
git worktree remove ./worktrees/<topic>; if the branch is fully merged, alsogit branch -d feature/<topic>. - One branch per worktree — git enforces this. For a second session on the same logical work, create a sibling branch.
- Shared module coordination — worktrees isolate the working tree, not the module graph. Two worktrees editing the same
packages/shared/<subpkg>/file at once will conflict at merge. Coordinate at the subpackage level; pick disjoint shared sub-packages per worktree. - Commit hygiene:
git status --shortbefore commit;git log -1 --statafter — confirms you committed what you intended. .git/index.lockin your worktree = your own prior git invocation crashed mid-flight. Investigate freely.
Inside a worktree, all git operations are private
git stash, git add -A, git restore, removing .git/index.lock — all safe inside your own worktree because the working tree is not shared with any other session.
Memory anchor: [[project_parallel_worktree_sessions]].
Skipping this rule requires explicit user approval in chat.
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.
- 2d ago First seen · 26 lines · 378 tokens per session scan A 48afde060a17
worktree-per-session is a cursor rule published in the GitHub repository AlphaBitCore/nexus-gateway (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 378 tokens to every session, about $0.0019 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 cursor rules, from other repositories
10-deterministic-audit
Enforce deterministic audit behavior — no invented controls, cite authoritative sources, emit traceable artifacts.
flagship_author
How to author a flagship in ks-cookbook.
recipe_author
How to author a recipe in ks-cookbook.
30-framework-routing
Route tasks to HIPAA, HITECH, PCI-DSS, SOC 2, ISO 27001, NIST CSF, NIST AI RMF, FERPA, COPPA, CCPA, US state privacy, GDPR, FedRAMP, SOX, CMMC, and GLBA skills based on user intent and presets.
00-compliance-agent-core
Core compliance agent mission, PHI redaction gate, and audit lifecycle for HIPAA, PCI-DSS, and SOC 2.
20-phi-redaction-first
PHI redaction first — Presidio gate, token handling, and minimum necessary LLM access for HIPAA workflows.