What is orchard-worktree-test?

A testing procedure for trying a locally built Orchard program from a separate Git worktree, an isolated checkout of a repository.

Building the worktree's release binary, temporarily pointing the orchard command to it, and restoring the original link afterward.

It lets you test worktree changes through the normal orchard command without permanently changing the main installation.

How drewdrewthis/orchardist configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to drewdrewthis/orchardist. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/drewdrewthis/orchardist/main/.claude/skills/orchard-worktree-test/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/drewdrewthis/orchardist

Made for: Claude Code.

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/drewdrewthis/orchardist/orchard-worktree-test/github.svg)](https://agentmods.dev/skills/drewdrewthis/orchardist/orchard-worktree-test)

Your own site

<a href="https://agentmods.dev/skills/drewdrewthis/orchardist/orchard-worktree-test"><img src="https://agentmods.dev/badge/skills/drewdrewthis/orchardist/orchard-worktree-test/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/drewdrewthis/orchardist/orchard-worktree-test"><img src="https://agentmods.dev/badge/skills/drewdrewthis/orchardist/orchard-worktree-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 815 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.00091	$0.00815
Opus 5	$0.00046	$0.00407
Sonnet 5	$0.00018	$0.00163
Haiku 4.5	$0.00009	$0.00081

Measured 9d ago against content hash 6e9e03da8d14, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

orchard-worktree-test 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 9d 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.

.claude/skills/orchard-worktree-test/SKILL.md · 60 lines

How it starts

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

Orchard Worktree Test

The orchard command in the user's shell is a symlink at ~/Library/pnpm/orchard that points at /Users/USER/workspace/orchardist/target/release/orchard (the main checkout's release build). To test a worktree's changes via the shell orchard command, the symlink must be temporarily repointed at the worktree's target/release/orchard.

Modes

Argument	Action
`test` (default)	Build the worktree, repoint symlink to it, prompt user to test
`revert`	Restore symlink to main checkout, no rebuild

Test Mode

Confirm working directory is a worktree. Run pwd — it should be under .worktrees/. If not, abort and tell the user this skill only makes sense in a worktree.
Build release in the worktree. Run cargo build --release (use ~/.claude/scripts/build-lock.sh global timeout 300 cargo build --release if the resource guard requires it). If the build fails, stop and report the error.
Capture the current symlink target so revert is reliable even if the user later forgets:
```
readlink ~/Library/pnpm/orchard
```
Save it to memory (state in your response) — typical value is /Users/USER/workspace/orchardist/target/release/orchard.

Repoint the symlink to the worktree's binary:

ln -sf <worktree-abs-path>/target/release/orchard ~/Library/pnpm/orchard

Verify with ls -la ~/Library/pnpm/orchard and confirm the new target.
Tell the user to test. Suggest specific things to verify based on the PR's changes (e.g., "scroll the preview pane", "open with 20+ worktrees"). Remind them the symlink is repointed and orchard in any shell now runs the worktree binary.
Wait for confirmation. Do not auto-revert. The user will say "looks good" / "merge it" / "revert" / "broken".

Revert Mode

Triggered by revert argument, or after the user confirms testing is done (success or failure):

Restore the symlink to the main checkout:

ln -sf /Users/USER/workspace/orchardist/target/release/orchard ~/Library/pnpm/orchard

Read the full file on GitHub · 60 lines

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.

9d ago First seen · 60 lines · 91 tokens per session scan A 6e9e03da8d14

Subscribe to this mod's changes

orchard-worktree-test is a skill published in the GitHub repository drewdrewthis/orchardist (5 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 815 once invoked, about $0.0005 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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

neuron-evaluation-engineer

Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…

neuron-core/neuron-ai · 77 tokens

orchardist: Skill for Claude Code