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/briangmilnes/apas-verus/create-worktreegit clone --depth 1 https://github.com/briangmilnes/APAS-VERUSWhat 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.00490 | $0.00490 |
| Opus 5 | $0.00245 | $0.00245 |
| Sonnet 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 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
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.
- 2d 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 1mo ago), licensed MIT. It adds 490 tokens to every session, about $0.0024 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.