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/qwickapps/ai-sdlc-workflows/worktree-enforcementgit clone --depth 1 https://github.com/qwickapps/ai-sdlc-workflowsWhat 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.01520 | $0.01520 |
| Opus 5 | $0.00760 | $0.00760 |
| Sonnet 5 | $0.00304 | $0.00304 |
| Haiku 4.5 | $0.00152 | $0.00152 |
Grade A, and why
WORKTREE-ENFORCEMENT 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 yesterday.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Enforcement
When to apply: Before creating ANY branch for feature/bug work. ALWAYS.
Core Principle
ALWAYS use the create-worktree script. NEVER use git worktree add or git checkout -b directly.
The script copies .env files, settings, and runs pnpm install. Skipping it breaks your development environment.
Reference: See COMMON-PATTERNS.md for checklist usage and stop/proceed logic.
The Problem
❌ What Keeps Happening (WRONG):
# Wrong approach 1
git checkout -b feature-auth
# Wrong approach 2
git worktree add ../qwickapps-wt-feature-auth -b feature-auth
# Result: Missing .env files, broken environment, wasted time debugging
✅ What Should Happen (RIGHT):
# Use the approved script
.claude/scripts/create-worktree.sh feature-auth
# OR from repo root
/Users/raajkumars/Projects/qwickapps/.claude/scripts/create-worktree.sh feature-auth
# Result: Worktree created, .env copied, pnpm install done, ready to work
Mandatory Worktree Checklist
Before creating ANY branch or worktree:
- STOP - Do not create branch/worktree yet
- FIND the create-worktree.sh script location
- USE the script (never git commands directly)
- VERIFY the script completed successfully
- CHANGE to the new worktree directory
If ANY unchecked: You're doing it wrong.
How to Find the Script
Option 1: Search from Current Directory
find ../.. -name "create-worktree.sh" -type f | head -1
# Likely: ../../.claude/scripts/create-worktree.sh
Option 2: From Repo Root
ls .claude/scripts/create-worktree.sh
Option 3: Known Path (QwickApps)
/Users/raajkumars/Projects/qwickapps/.claude/scripts/create-worktree.sh
When to Create Worktrees
Required for:
- New feature development (
/featureworkflow) - Bug fixes (
/bugworkflow) - Refactoring (
/refactorworkflow) - Experimental spikes (
/spikeworkflow)
Every workflow mentioning "create worktree" MUST reference this file.
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.
- yesterday First seen · 263 lines · 1,520 tokens per session scan A dd975499c888
WORKTREE-ENFORCEMENT is a cursor rule published in the GitHub repository qwickapps/ai-sdlc-workflows (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,520 tokens to every session, about $0.0076 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
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
pro-deck-builder
Create polished HTML slide decks and PDF-ready documents for consulting deliverables. Uses the RRBC design system with warm light mode, dark mode cover pages, Lora/Inter/Roboto Mono typography, and data visualization palette. Trigger on 'deck', 'slides', 'presentation', 'pitch deck', 'keynote', 'report', or 'PDF'.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
facebook-ads
Meta Ads (Facebook & Instagram) platform expertise. Audit campaigns, audiences, creative strategy, pixel tracking, and CAPI. Use when the user asks about Facebook Ads, Instagram Ads, Meta Ads, social media advertising, Advantage+ campaigns, or Meta pixel/CAPI setup.
paddle-integration
Conventions for Paddle integration code.
faststore-faststore-storefront-ref-project-structure-routes-and-config
FastStore project structure, routes, CLI build pipeline, store configuration (discovery.config.js), and naming conventions. Use when understanding how a FastStore project is organized, how the @faststore/cli works, what files to create or modify, how routing works, or how to configure store settings like SEO, API…