Borrowing it
Nothing to install: this file belongs to adarshp14/relay. 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/adarshp14/relay/main/.skills/cli-release/SKILL.mdgit clone --depth 1 https://github.com/adarshp14/relayWrote 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/skills/adarshp14/relay/cli-release)<a href="https://agentmods.dev/skills/adarshp14/relay/cli-release"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/cli-release/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/skills/adarshp14/relay/cli-release"><img src="https://agentmods.dev/badge/skills/adarshp14/relay/cli-release.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.00080 | $0.02132 |
| Opus 5.5 | $0.00032 | $0.00853 |
| Sonnet 5.5 | $0.00016 | $0.00426 |
| Haiku 4.5 | $0.00008 | $0.00213 |
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 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.
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 — 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 + daemonapps/local/**— the web UI (embedded as a virtual module viaapps/cli/src/build.ts:178) + drizzle migrations (build.ts:205)packages/**—core,kernel,hosts/mcp,runtime-quickjs, and every plugin underpackages/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
patchbumps for feature-heavy releases (see.changeset/relay-1.4.6-beta.mdfor 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
patchbumps. Follow the owner's call — ask, don't assumeminor. - Normal release/patch PRs must add a
.changeset/*.mdfile with frontmatter like"relay": patch. Do not directly bumpapps/cli/package.jsonorbun.lockin a feature/fix PR. - Only the Changesets-generated
Version PackagesPR should moveapps/cli/package.json. If a normal PR directly changes that version, merging it tomaincan make.github/workflows/release.ymltag the commit and dispatchpublish-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.
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.
- 1mo ago First seen · 156 lines · 80 tokens per session scan A 89b39d98a7cb
cli-release is a skill published in the GitHub repository adarshp14/relay (0 stars, last pushed 4mo ago), licensed MIT. It adds 80 tokens to every session and 2,132 once invoked, about $0.0003 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 skills, from other repositories
release
Release vercel-plugin — run gates, bump version, generate artifacts, commit, and push. Use when asked to "release", "ship", "bump and push", or "cut a release".
changelog-style
Turn a commit range into CHANGELOG.md entries following common-changelog style. Use when finishing a PR (adding to the [Unreleased] section) or cutting a release (moving [Unreleased] under a new version heading).
release
Cut a release of steam-games-mcp — draft CHANGELOG entries, check docs/metadata consistency, then bump/tag/push. Use when asked to release, cut a version, or publish a new version of this package.
lathe-release
Run Lathe release validation and publishing workflows. Use when the user asks to prepare, validate, cut, tag, publish, or ship a Lathe versioned release; runs the captured pre-release regression gate before tagging.
ship-cycle
Issue-driven development orchestrator. Turns improvement intent into a well-specified, bilingual issue set; clusters issues into milestones that map 1:1 to semver versions; enforces branch, commit, and PR conventions (GitHub Flow — / - , Conventional Commits, mandatory PR template, rebase-first merge); generates…
gitea-webhooks
Receive and verify Gitea webhooks. Use when setting up Gitea webhook handlers, debugging X-Gitea-Signature verification, or handling self-hosted Git events like push, pullrequest, issues, issuecomment, create, delete, or release.