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 skills/lonormaly/builders-stack/create-a-worktreenpx skills add lonormaly/builders-stack --skill create-a-worktreegit clone --depth 1 https://github.com/lonormaly/builders-stackWrote 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/skills/lonormaly/builders-stack/create-a-worktree)<a href="https://agentmods.dev/skills/lonormaly/builders-stack/create-a-worktree"><img src="https://agentmods.dev/badge/skills/lonormaly/builders-stack/create-a-worktree.svg" alt="Measured on agentmods" 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.00037 | $0.00526 |
| Opus 5 | $0.00018 | $0.00263 |
| Sonnet 5 | $0.00007 | $0.00105 |
| Haiku 4.5 | $0.00004 | $0.00053 |
Grade A, and why
create-a-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 today.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a Builders Stack worktree
Use the repository adapter. It keeps project policy in Builders Stack while the
generic source and runtime lifecycle comes from the single wt0 binary.
Create
- Preserve every existing change in the current checkout.
- Confirm
ops/dev/wt0.sh --versionreports the version pinned in.wt0-versionand Bun 1.3.14 is available. The launcher verifies the release checksum before caching the binary. - From the main checkout, run:
ops/dev/worktree.sh <namespaced-branch>
Use the absolute path it prints. Do not call raw git worktree, copy the repo,
copy node_modules, or share a complete mutable dependency directory.
The wrapper requires copy-on-write source and attaches the verified Bun
prepared environment before reporting the checkout ready.
Work and inspect
- Start the stack only through the checkout's normal project command.
- Use
ops/dev/wt0.sh doctor <path>when storage or dependency sharing is in doubt. - Keep the returned branch and path as the runtime identity for later cleanup.
- Treat Finder and
duas logical size only. Use the Worktree Zero physical receipt when reporting actual disk allocation.
Remove
After the patch is present in origin/main, leave the checkout and run:
ops/dev/worktree.sh --rm <branch>
The adapter refuses dirty source, unknown ignored files, live processes,
unmerged patches, and unpreserved merge commits. Never force past a refusal.
Use ops/dev/worktree.sh --gc to evaluate finished managed worktrees; it keeps
anything that fails the same safety checks. Provenance for these checks isn't
tied to the wrapper alone: a worktree created straight through wt0 create or
wt0 run (bypassing this wrapper entirely) is just as safely removable — wt0's
own fleet record proves ownership in place of the wrapper's marker file. Prefer
ops/dev/worktree.sh <branch> above for the extra guardrails (Bun-version
floor, prepared environment, worktree cap, free-disk floor), but a bare
wt0 create/wt0 run checkout still tears down cleanly through wt0 remove.
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.
- today First seen · 55 lines · 37 tokens per session scan A f126ca0b8ba4
create-a-worktree is a skill published in the GitHub repository lonormaly/builders-stack (41 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 526 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-propose
Propose a new change with all artifacts generated in one step. Use when the user wants to quickly describe what they want to build and get a complete proposal with design, specs, and tasks ready for implementation.
openspec-sync-specs
Sync delta specs from a change to main specs. Use when the user wants to update main specs with changes from a delta spec, without archiving the change.
openspec-archive-change
Archive a completed change in the experimental workflow. Use when the user wants to finalize and archive a change after implementation is complete.
scaffold-project
Scaffold a new app, API, backend, fullstack project, monorepo, or starter with Better-T-Stack — including new projects built on a specific framework like Hono, Express, Fastify, Elysia, Next.js, TanStack Router/Start, Nuxt, Svelte, Solid, Astro, or React Native (native-bare, native-uniwind, native-unistyles). Use…
add-to-project
Add addons or features (PWA, Tauri, Starlight/Fumadocs docs, Biome/Oxlint, Husky/Lefthook, Turborepo/Nx, the MCP addon, etc.) to an existing Better-T-Stack project. Use when the user wants to extend, enhance, or add tooling to a project that was created with Better-T-Stack.