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/shapediver/AppBuilderSdkWrote 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/shapediver/appbuildersdk/worktree-shared-repo)<a href="https://agentmods.dev/rules/shapediver/appbuildersdk/worktree-shared-repo"><img src="https://agentmods.dev/badge/rules/shapediver/appbuildersdk/worktree-shared-repo/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/shapediver/appbuildersdk/worktree-shared-repo"><img src="https://agentmods.dev/badge/rules/shapediver/appbuildersdk/worktree-shared-repo.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.00480 | $0.00480 |
| Opus 5.5 | $0.00192 | $0.00192 |
| Sonnet 5.5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
worktree-shared-repo 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
Worktree + AppBuilderShared
New Cursor worktrees often have an empty src/shared and hide Shared diffs in Changes (nested repo / Cursor git.autoRepositoryDetection default). Do not rely on hooks alone.
Every agent MUST proactively perform these setup checks at the start of any task or when working in a worktree:
- Verify and initialize submodule:
- Check if
src/sharedhas.git. If not or if submodule is uninitialized, run:
(orgit submodule init git submodule updategit submodule update --init -- src/shared).
- Check if
- Ensure
.vscode/settings.jsonis created:.vscode/settings.jsonis gitignored and is frequently missing in newly created worktrees.- Agents MUST check if
.vscode/settings.jsonexists. If missing or incomplete, immediately create/write it:{ "git.autoRepositoryDetection": true, "git.detectSubmodules": true, "git.repositoryScanMaxDepth": 2, "git.scanRepositories": [ "src/shared" ] }
- Branch synchronization:
- Ensure
task/JIRA-ISSUE-IDis checked out in both the root repo andsrc/shared(git -C src/shared checkout ...).
- Ensure
- Source Control / Changes visibility in the IDE:
- If changes in
src/shareddo not appear in the Source Control panel: a. Instruct/perform Source Control tab refresh (refresh icon in Source Control view). b. If still not visible, reload the window (Developer: Reload WindowviaCtrl+Shift+P/F1). c. Or addsrc/sharedas a multi-root workspace folder (File > Add Folder to Workspace...).
- If changes in
- Git workflow for shared:
- Shared git operations:
git -C src/shared .... - The root repo only updates its submodule pointer (
src/shared) aftersrc/sharedhas been committed.
- Shared git operations:
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 Changed · +24 lines · +218 tokens per session bd5b306ac731
- 1mo ago First seen · 18 lines · 262 tokens per session scan A f71ef477b122
worktree-shared-repo is a cursor rule published in the GitHub repository shapediver/AppBuilderSdk (15 stars, last pushed yesterday), licensed MIT. It adds 480 tokens to every session, about $0.0019 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-09-10.
Other cursor rules, from other repositories
git
A set of Git workflow and branch-naming instructions for the Alibaba Hooks codebase. Git is a tool for tracking code changes, while a branch is a separate line of work that can later be proposed for merging.
release-lanes
Promote Plate beta releases, sync main back to next and verify published npm/GitHub state with release authority.
changeset
Write and verify package release changesets, registry changelog entries, and the PR’s managed auto-release choice. Use before deciding whether a package edit needs a changeset, including skipping one.
release-process
Use the documented Windows and macOS release flow.
git-flow
Branching, commits and PR hygiene. Always applies.
ci-cd-workflows
This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…