What is setup-convex-worktrees?

A setup guide for giving each Git worktree—an additional checkout of the same repository—its own temporary Convex development deployment and frontend settings.

It helps configure per-worktree environment variables, temporary Convex deployments, baseline data, separate frontend ports, and repository instructions for agents.

It prevents separate checkouts and coding agents from overwriting one shared development backend or using inconsistent test data.

setup-convex-worktrees — Skill for Codex by mackinleysmith

Install

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.

Any agent

npx skills add mackinleysmith/convex-worktree-isolation --skill setup-convex-worktrees

Clone the repo

git clone --depth 1 https://github.com/mackinleysmith/convex-worktree-isolation

Made for: Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/mackinleysmith/convex-worktree-isolation/setup-convex-worktrees/github.svg)](https://agentmods.dev/skills/mackinleysmith/convex-worktree-isolation/setup-convex-worktrees)

Your own site

<a href="https://agentmods.dev/skills/mackinleysmith/convex-worktree-isolation/setup-convex-worktrees"><img src="https://agentmods.dev/badge/skills/mackinleysmith/convex-worktree-isolation/setup-convex-worktrees/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/mackinleysmith/convex-worktree-isolation/setup-convex-worktrees"><img src="https://agentmods.dev/badge/skills/mackinleysmith/convex-worktree-isolation/setup-convex-worktrees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 95 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,509 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00095	$0.01509
Opus 5.5	$0.00038	$0.00604
Sonnet 5.5	$0.00019	$0.00302
Haiku 4.5	$0.00010	$0.00151

Measured 2mo ago against content hash 3b4719a91dfd, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-convex-worktrees 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 2mo ago.

The scan reads SKILL.md. This mod also ships 6 executable files (assets/template/convex/schema.snippet.ts, assets/template/convex/seed.ts, assets/template/scripts/next-dev.mjs, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/setup-convex-worktrees/SKILL.md · 177 lines

How it starts

The opening of the file, as written. The whole thing — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set Up Convex Worktrees

Give each linked Git worktree a short-lived Convex dev deployment, coherent baseline data, and an explicit agent invariant. Adapt the bundled implementation to the target repository instead of imposing its example layout or schema.

Workflow

1. Inspect before editing

Read every applicable repository instruction file.
Inspect the worktree state and preserve unrelated changes.
Identify:
- the package manager and repository root;
- the Convex package version and directory;
- backend and frontend env files;
- the frontend's public Convex URL variable;
- existing dev scripts, seed functions, and worktree tooling;
- authentication, scheduled jobs, webhooks, and provider side effects.
Read convex/_generated/ai/guidelines.md completely when present. If it is missing or stale, recommend npx convex ai-files install.
Read references/adaptation.md before choosing paths, seed behavior, or a validation strategy.

Do not assume a monorepo. Do not replace compatible existing tooling merely to match the templates.

2. Choose the installation shape

Use the smallest shape that solves the collision:

Always isolate the Convex dev deployment.
Sync a separate client env file only when the Convex CLI does not already write the frontend's public URL variable.
Add port isolation only when multiple frontend dev servers will run.
Mirror only non-secret, checkout-specific values to the deployment.
Keep remote tunnels, process supervisors, and hosting previews outside this skill unless the user explicitly includes them.

Require Convex 1.34.0 or later for deployment selection by reference. Prefer the repository's installed Convex CLI over a global version.

3. Install the provisioner

For a new installation, run the bundled no-overwrite copier:

node <skill-dir>/scripts/copy-template.mjs --target <repository-root>

Add --next only for a Next.js app that needs .env.local PORT support:

Read the full file on GitHub · 177 lines

Files

What ships with it

9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

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.

2mo ago First seen · 177 lines · 95 tokens per session scan A 3b4719a91dfd

Subscribe to this mod's changes

setup-convex-worktrees is a skill published in the GitHub repository mackinleysmith/convex-worktree-isolation (2 stars, last pushed 3mo ago), licensed MIT. It adds 95 tokens to every session and 1,509 once invoked, about $0.0004 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.

Cloud DevOps and cloud Git and workflow ai-agents convex developer-tools git-worktrees

setup-convex-worktrees

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Set Up Convex Worktrees

Workflow

1. Inspect before editing

2. Choose the installation shape

3. Install the provisioner

What ships with it

What this file has done since we first saw it

Other skills, from other repositories

land-and-deploy

publish-site

release-publish

release-review

orchard-release

orchard-review