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/briangmilnes/APAS-VERUSWrote 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/briangmilnes/apas-verus/create-worktree)<a href="https://agentmods.dev/rules/briangmilnes/apas-verus/create-worktree"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/create-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/rules/briangmilnes/apas-verus/create-worktree"><img src="https://agentmods.dev/badge/rules/briangmilnes/apas-verus/create-worktree.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.00490 | $0.00490 |
| Opus 5.5 | $0.00196 | $0.00196 |
| Sonnet 5.5 | $0.00098 | $0.00098 |
| Haiku 4.5 | $0.00049 | $0.00049 |
Grade A, and why
create-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
Create Agent Worktree
Naming convention
| Worktree | Directory | Branch prefix |
|---|---|---|
| main | ~/projects/APAS-VERUS |
main |
| agent1 | ~/projects/APAS-VERUS-agent1 |
agent1/ |
| agent2 | ~/projects/APAS-VERUS-agent2 |
agent2/ |
| agent3 | ~/projects/APAS-VERUS-agent3 |
agent3/ |
Branch names follow the pattern agentN/<topic> (e.g., agent1/verusify-chap37).
Creating a worktree
# From the main worktree
cd ~/projects/APAS-VERUS
# Create agent1 worktree with a topic branch
git worktree add -b agent1/<topic> ~/projects/APAS-VERUS-agent1 main
# Create agent2 worktree with a topic branch
git worktree add -b agent2/<topic> ~/projects/APAS-VERUS-agent2 main
# Create agent3 worktree with a topic branch
git worktree add -b agent3/<topic> ~/projects/APAS-VERUS-agent3 main
Switching an agent's topic
When an agent finishes a topic and starts a new one, rename the branch — don't recreate the worktree:
# In the agent worktree (e.g., ~/projects/APAS-VERUS-agent1)
git checkout main
git pull origin main
git checkout -b agent1/<new-topic>
Removing a worktree
cd ~/projects/APAS-VERUS
git worktree remove ~/projects/APAS-VERUS-agent1
git branch -d agent1/<topic>
# Similarly for agent2, agent3:
# git worktree remove ~/projects/APAS-VERUS-agent2
# git worktree remove ~/projects/APAS-VERUS-agent3
Rules
- Each agent works ONLY in its own worktree directory. Never
cdinto another agent's worktree. - Main is the integrator. Agents do not push to main directly.
- Agents push their own branches:
git push origin agent1/<topic>. - Main merges agent branches one at a time (see merge-worktree rule).
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 · 59 lines · 490 tokens per session scan A 2ae7cd957b59
create-worktree is a cursor rule published in the GitHub repository briangmilnes/APAS-VERUS (10 stars, last pushed 23d ago), licensed MIT. It adds 490 tokens to every session, about $0.0020 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-31.
Other cursor rules, from other repositories
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
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.