setup

setup is a skill for Claude Code from open-horizon-labs/repo-native-alignment. It costs 42 tokens per session (2,563 once invoked), scanned A, original, MIT.

A setup skill for installing and configuring Repo-Native Alignment, a tool that helps coding agents understand a repository’s code and goals.

In plain words
What is it for?
It is for checking or installing the service, configuring its MCP connection, warming its code index, and updating AGENTS.md with usage guidance.
Why use it?
It prepares the code-intelligence service and its project guidance so later agents can find relevant code and understand how changes fit the repository.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions Claude Code; mentions AGENTS.md.

Not installable: its command points at a path on the author’s own machine, so it runs nowhere else. The line is /Users/me/.cargo/bin/repo-native-alignment.

Part of the rna-mcp plugin — 6 skills, 1 command shipped together

Good fit It is for checking or installing the service, configuring its MCP connection, warming its code index, and updating AGENTS.md with usage guidance.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add open-horizon-labs/repo-native-alignment
Claude Code
/plugin install rna-mcp

Made for: Claude Code.

Or install rna-mcp, the plugin that ships this one along with the rest of its 6 skills, 1 command.

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.

agentmods badge for setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/setup/github.svg)](https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/setup)
Your own site
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/setup"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/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.

agentmods 80×15 button for setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/open-horizon-labs/repo-native-alignment/setup"><img src="https://agentmods.dev/badge/skills/open-horizon-labs/repo-native-alignment/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,563 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.02563
Opus 5.5 $0.00017 $0.01025
Sonnet 5.5 $0.00008 $0.00513
Haiku 4.5 $0.00004 $0.00256

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

Security

Grade A, and why

setup scanned grade A with 1 finding 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 1mo 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -L https://github.com/open-horizon-labs/repo-native-alignment/releases/latest/download/repo-native-alignment-darwin-arm64-fast.tar.gz | tar xz -C ~/.cargo/bin
plugin/skills/setup/SKILL.md · 222 lines

How it starts

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

Setup Repo-Native Alignment MCP

Install the RNA MCP server for aim-conditioned code intelligence.

Execute these steps in order. Do not stop between steps or ask for confirmation -- run the full sequence automatically.

Step 1: Check if already installed

which repo-native-alignment 2>/dev/null

If found, skip to Step 3. If not found, proceed to Step 2.

Step 2: Download the binary

Detect the platform and chip, then download to ~/.cargo/bin/ (already on PATH for Rust users):

OS=$(uname -s)
ARCH=$(uname -m)
CHIP=$(sysctl -n machdep.cpu.brand_string 2>/dev/null || echo "")
mkdir -p ~/.cargo/bin

If macOS ARM M2+ (Darwin + arm64 + brand_string contains "M2", "M3", or "M4"):

curl -L https://github.com/open-horizon-labs/repo-native-alignment/releases/latest/download/repo-native-alignment-darwin-arm64-fast.tar.gz | tar xz -C ~/.cargo/bin

If macOS ARM (M1) (Darwin + arm64):

curl -L https://github.com/open-horizon-labs/repo-native-alignment/releases/latest/download/repo-native-alignment-darwin-arm64.tar.gz | tar xz -C ~/.cargo/bin

If Linux x86_64 (Linux + x86_64):

curl -L https://github.com/open-horizon-labs/repo-native-alignment/releases/latest/download/repo-native-alignment-linux-x86_64.tar.gz | tar xz -C ~/.cargo/bin

If none of the above match: Tell the user their platform is not yet supported by the published release artifacts. They may build from source for development/testing, but source builds are not a substitute for release verification from successful CI/release artifacts:

cargo install --locked --git https://github.com/open-horizon-labs/repo-native-alignment

If ~/.cargo/bin is not on PATH (no Rust toolchain installed), tell the user to add it: export PATH="$HOME/.cargo/bin:$PATH"

Release artifacts are intentionally built without local embedding/reranking support. They support extraction, graph traversal, lexical search, LSP call/reference enrichment, repo maps, and MCP delivery. Semantic search and cross-encoder reranking require a development/source build with embedding features (Apple Silicon Metal: cargo install --locked --path . --features metal from a checked-out repo); source builds are not a substitute for release verification from successful CI/release artifacts.

Read the full file on GitHub · 222 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.

  1. 1mo ago First seen · 222 lines · 42 tokens per session scan A 4908153801da

Subscribe to this mod's changes

setup is a skill published in the GitHub repository open-horizon-labs/repo-native-alignment (6 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 2,563 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…

vercel/next.js · 123 tokens