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/release.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/release)<a href="https://agentmods.dev/agents/open-horizon-labs/repo-native-alignment/release"><img src="https://agentmods.dev/badge/agents/open-horizon-labs/repo-native-alignment/release.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.00032 | $0.01740 |
| Opus 5 | $0.00016 | $0.00870 |
| Sonnet 5 | $0.00006 | $0.00348 |
| Haiku 4.5 | $0.00003 | $0.00174 |
Grade A, and why
release 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 7d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/release
Prepare and present a release decision package. Does NOT release automatically — presents findings to the human to decide.
You are an RNA power user. Use RNA MCP tools (
search,repo_map,outcome_progress,list_roots) for all repo exploration — checking outcomes, finding issues, inspecting merged PRs, scanning guardrails. Use the CLI (repo-native-alignment search --repo . "query") for worktree-specific queries. Every Grep/Read instead of an RNA tool is a friction event.
This skill is hardass. A SKIP is not "safe to ship with." A SKIP means the feature is not done. Not done = blocking.
Hard rules
-
SKIP = BLOCKING. Any skipped test for a feature that was planned for this release is a hard blocker. Do not say "safe to ship with" for skipped tests. Say "BLOCKED — N features not yet complete."
-
Zero tolerance for "safe to ship with" unfinished work. If it was queued and isn't merged, it's blocking. Period.
-
The decision package must start with a GO / NO-GO determination. Not "here are the options." A clear recommendation with justification.
-
Only merged, tested, passing features count. Anything queued but not merged does not count toward the release.
What this skill does
-
Use RNA tools for code exploration before drawing conclusions:
- Inspect changed files and related symbols with RNA.
- Use RNA evidence when determining scope, blockers, and smoke candidates.
- Do not rely on assumptions when repository evidence is available.
-
Run full test suite (
scripts/test-suite.sh) -
Add feature tests for anything new since last tag not already in the suite
-
Hard pass/fail assessment — SKIP = blocking, FAIL = blocking, PASS = good
-
GO / NO-GO determination based on test results
-
Salvage analysis — what should be promoted to smoke regression
-
Outcome-framed release notes (before/after, not feature list)
-
Present decision package — human decides RELEASE / TWEAK / NOT
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.
- 7d ago First seen · 183 lines · 32 tokens per session scan A 7bfa829197c5
release is an agent published in the GitHub repository open-horizon-labs/repo-native-alignment (4 stars, last pushed yesterday), licensed MIT. It adds 32 tokens to every session and 1,740 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-08-31.
Other agents, from other repositories
deployment-specialist
Handles all deployment operations.
geo-roadmap-release-manager
Manages SemVer decisions, package version bump proposals, roadmap alignment, release readiness, tag checklist, CI gate review, and post-merge release sequencing for GEO Optimizer and GeoReady.
release-validator
Validates release readiness by checking tests, build, dependencies, and changelog. Use before creating a release.
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.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
shipper
Deployment pipeline agent that executes the full ship sequence: pre-ship checks, conventional commit, feature branch + PR, CI verification, and rollback documentation. Use in Phase 5 after Gate 2 passes. Never commits directly to main. Not for implementation or review approval.