Borrowing it
Nothing to install: this file belongs to JimmyPaolini/codebase. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/JimmyPaolini/codebase/main/.github/instructions/using-git-worktrees.instructions.mdgit clone --depth 1 https://github.com/JimmyPaolini/codebaseWrote 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/instructions/jimmypaolini/codebase/using-git-worktrees)<a href="https://agentmods.dev/instructions/jimmypaolini/codebase/using-git-worktrees"><img src="https://agentmods.dev/badge/instructions/jimmypaolini/codebase/using-git-worktrees.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.00347 | $0.00347 |
| Opus 5 | $0.00173 | $0.00173 |
| Sonnet 5 | $0.00069 | $0.00069 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
codebase using-git-worktrees.instructions.md 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 3d 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
Git Worktree Workflow
Use the using-git-worktrees
skill to create or verify an isolated workspace. It prefers a native worktree
tool when one is available and falls back to git worktree otherwise — either
way, avoid ad hoc git worktree add invocations.
Two repository rules override the skill's generic defaults:
- Branch names are validated. Use the
<type>/<scope>-<description>format defined byconfiguration/conventional.config.cjs. The authoritative type and scope tables live in the Conventional Naming section ofAGENTS.md, which theconventional-configsynchronization target keeps in sync — read them there rather than from a copy. Derive a compliant name with the checkout-branch skill when the user gives only an intent. - Validate before creating anything: run
pnpm exec validate-branch-name -t "<branch-name>". The pre-push hook and the Validate Conventions workflow both reject a non-compliant branch.
If the branch already exists locally, attach a worktree to it instead of creating a replacement branch.
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.
- 3d ago First seen · 28 lines · 347 tokens per session scan A 007b1dd93ac3
codebase using-git-worktrees.instructions.md is an instructions file published in the GitHub repository JimmyPaolini/codebase (0 stars, last pushed today), licensed MIT. It adds 347 tokens to every session, about $0.0017 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-03.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.