A release procedure for the Relay command-line package and its beta versions. It defines which parts of the repository ship, how changelogs are written, and how Changesets and version-package pull requests are used.

Preparing releases, writing release notes, managing version pull requests, and entering or leaving a beta release cycle.

It prevents release notes and version changes from covering the wrong code, especially when the CLI includes embedded UI and shared packages.

cli-release — Skill by adarshp14

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add skills/adarshp14/relay/cli-release

Any agent

npx skills add adarshp14/relay --skill cli-release

Clone the repo

git clone --depth 1 https://github.com/adarshp14/relay

Made for: Claude Code, Codex.

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

When invoked 2,132 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00080	$0.02132
Opus 5	$0.00040	$0.01066
Sonnet 5	$0.00016	$0.00426
Haiku 4.5	$0.00008	$0.00213

Measured yesterday against content hash 89b39d98a7cb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cli-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 yesterday.

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.

.skills/cli-release/SKILL.md · 156 lines

How it starts

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

Relay CLI release runbook

Authoritative doc

RELEASING.md at repo root is the source of truth. This skill encodes the owner's preferences on top of it.

What the `relay` CLI actually ships

The CLI binary bundles:

apps/cli/** — CLI source + daemon
apps/local/** — the web UI (embedded as a virtual module via apps/cli/src/build.ts:178) + drizzle migrations (build.ts:205)
packages/** — core, kernel, hosts/mcp, runtime-quickjs, and every plugin under packages/plugins/**

Does not ship in the CLI:

apps/cloud/** (Cloudflare Workers deployment)
apps/marketing/**, apps/desktop/**
examples/**, tests/**

Implication for changelogs: when asked "what changed since the last release", scope is git log v<last>..HEAD -- apps/cli apps/local packages, not just apps/cli. Skipping apps/local and packages misses the bulk of product changes (Connections UI, OAuth plugins, SDK scope, OTEL, etc.).

Versioning preferences

Prior convention in this repo uses patch bumps for feature-heavy releases (see .changeset/relay-1.4.6-beta.md for precedent). Don't push back on patch unless there are genuine SemVer-breaking API changes to a library consumer surface.
Breaking CLI UX changes (removed flags, changed argv shape) have historically still been patch bumps. Follow the owner's call — ask, don't assume minor.
Normal release/patch PRs must add a .changeset/*.md file with frontmatter like "relay": patch. Do not directly bump apps/cli/package.json or bun.lock in a feature/fix PR.
Only the Changesets-generated Version Packages PR should move apps/cli/package.json. If a normal PR directly changes that version, merging it to main can make .github/workflows/release.yml tag the commit and dispatch publish-relay-package.yml, causing an immediate CLI publish.
@relay-sh/* library packages have their own publish path.

Release notes: single source of truth, curated, not auto-generated

The owner doesn't want GitHub's auto-generated "PR title by @user" list. Release notes live at apps/cli/release-notes/ and apps/cli/src/release.ts prefers them over --generate-notes.

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

yesterday First seen · 156 lines · 80 tokens per session scan A 89b39d98a7cb

Subscribe to this mod's changes

cli-release is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 2mo ago), licensed MIT. It adds 80 tokens to every session and 2,132 once invoked, about $0.0004 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.

Backend and APIs Data and AI Git and workflow ai-agents graphql llm-tools mcp openapi typescript

create-tutorial

Scaffold a new Membrane API Gateway tutorial in the api-gateway repo — the numbered self-teaching YAML under distribution/tutorials/ /, its support files and README links, and the matching auto-discovered integration test. Use whenever the user asks to create, add, write, or scaffold a tutorial (or a tutorial step)…

membrane/api-gateway · 97 tokens

optimize-interceptor-docs

Rewrite the reference documentation of a Membrane config element so the page generated at membrane-api.io comes out clean, exact, and reference-style. Use whenever the user wants to write, improve, optimize, polish, or review the docs / Javadoc / @description / @yaml example of an interceptor, plugin, or any…

membrane/api-gateway · 173 tokens

review-branch

Review the current git branch against master — code quality, refactoring opportunities, regressions, correctness, and test coverage — and print a severity-grouped markdown report. Use whenever the user asks to review the branch, review their changes against master, do a pre-PR / pre-merge review, or asks "is this…

membrane/api-gateway · 125 tokens

membrane-config

Generate a Membrane API Gateway configuration example or snippet — an apis.yaml (default) or, when explicitly asked, a legacy proxies.xml. Use this whenever the user wants a config, example, or snippet for Membrane: routing a port to a backend, a flow with plugins (setHeader, rateLimiter, basicAuthentication, openapi…

membrane/api-gateway · 167 tokens

release-notes

Generate GitHub release notes for the Membrane api-gateway repo by collecting the commits between the last release and master, grouping them into Features / Improvements / Fixes / Security / Dependencies, and linking each to its PR. Use whenever the user wants to draft, extract, or write release notes / a changelog /…

membrane/api-gateway · 124 tokens

mcp2cli

Turn any MCP server, OpenAPI spec, or GraphQL endpoint into a CLI. Use this skill when the user wants to interact with an MCP server, OpenAPI/REST API, or GraphQL API via command line, discover available tools/endpoints, call API operations, or generate a new skill from an API. Triggers include "mcp2cli", "call this…

knowsuchagency/mcp2cli · 126 tokens