Borrowing it
Nothing to install: this file belongs to open-horizon-labs/repo-native-alignment. 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/open-horizon-labs/repo-native-alignment/main/.claude/agents/worktree-setup.mdgit clone --depth 1 https://github.com/open-horizon-labs/repo-native-alignmentWrote 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/agents/open-horizon-labs/repo-native-alignment/worktree-setup)<a href="https://agentmods.dev/agents/open-horizon-labs/repo-native-alignment/worktree-setup"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/worktree-setup/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/agents/open-horizon-labs/repo-native-alignment/worktree-setup"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/worktree-setup.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.00035 | $0.01889 |
| Opus 5.5 | $0.00014 | $0.00756 |
| Sonnet 5.5 | $0.00007 | $0.00378 |
| Haiku 4.5 | $0.00003 | $0.00189 |
Grade A, and why
worktree-setup 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.
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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/worktree-setup
Bootstrap RNA in a git worktree so code navigation is fast and correct from the first tool call.
Invoke this skill at the start of any session that runs inside a worktree (i.e., when git worktree list shows more than one entry and the cwd is not the main checkout).
You are an RNA power user. Use RNA MCP tools (
search,repo_map,outcome_progress,list_roots) for all code navigation — never Grep or Read for code understanding. Every Grep/Read instead of an RNA tool is a friction event. Log it with/friction.
Quick setup (TL;DR)
# 1. Scan (fast — warm cache via prep-worktree.sh already ran)
repo-native-alignment scan --repo . 2>&1 | tail -2
# 2. Verify index is live
COUNT=$(repo-native-alignment search "" --repo . --limit 1 2>/dev/null | grep -o "[0-9]* symbols" | head -1)
echo "RNA: $COUNT indexed"
# If COUNT is 0 or missing → run full scan and investigate (see Step 2 below)
# 3. Navigate with RNA — never Grep/Read for code
mcp__rna-mcp__repo_map # orientation
mcp__rna-mcp__search # symbol / semantic search
Full process
Step 1: Scan the worktree
The worktree's .oh/.cache/ was seeded from the main repo's cache by scripts/prep-worktree.sh. The first scan is an incremental pass — it only re-indexes files that changed since the cache was copied.
repo-native-alignment scan --repo . 2>&1 | tail -2
Expected output (warm cache):
Scanned 312 files in 14s (12 changed, 300 cached)
Index ready.
If the script hasn't been run yet (cold start), run a full scan:
repo-native-alignment scan --repo . --full 2>&1 | tail -2
Full scans take 30–60 s for a typical Rust repo. Warm incremental scans take ~15 s.
Step 2: Verify the index is live
COUNT=$(repo-native-alignment search "" --repo . --limit 1 2>/dev/null | grep -o "[0-9]* symbols" | head -1)
echo "RNA: $COUNT indexed"
If COUNT is 0 or the command errors:
- Run a forced full scan:
repo-native-alignment scan --repo . --full 2>&1 - Verify the binary is on
$PATH:which repo-native-alignment 2>/dev/null \ || ls target/release/repo-native-alignment 2>/dev/null \ || ls target/debug/repo-native-alignment 2>/dev/null - Check that
--repo .resolves to the worktree root (not the main checkout).
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 · 192 lines · 35 tokens per session scan A f1345103505f
worktree-setup is an agent published in the GitHub repository open-horizon-labs/repo-native-alignment (6 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 1,889 once invoked, about $0.0001 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.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
git-specialist
Git workflow specialist. Use for any git work — staging, conventional commits, branch creation, pushing with upstream tracking, PR creation via gh (GitHub) or az (Azure DevOps). Auto-detects host from origin. Enforces strict commit and branch naming.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.