A release procedure for publishing new versions of the Cyrus command-line tool and its related packages. A release is the checked and coordinated process of preparing code, creating a pull request, merging it, and publishing it.

Use it when releasing Cyrus, publishing cyrus-ai, or running the project's release workflow. It prepares changelogs, updates package versions, runs release tests, validates the result, and publishes from the main branch.

It provides an ordered checklist for version changes, dependency installation, testing, validation, and trusted publishing. This reduces the risk of releasing untested code or mismatched package versions.

release — Skill for Claude Code and Codex by cyrusagents/cyrus

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.

Any agent

npx skills add cyrusagents/cyrus --skill release

Clone the repo

git clone --depth 1 https://github.com/cyrusagents/cyrus

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/cyrusagents/cyrus/release/github.svg)](https://agentmods.dev/skills/cyrusagents/cyrus/release)

Your own site

<a href="https://agentmods.dev/skills/cyrusagents/cyrus/release"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/cyrusagents/cyrus/release"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/release.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 684 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 24 Sept 2026
Snyk pass 24 Sept 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.1	$0.00042	$0.00684
Opus 5.5	$0.00017	$0.00274
Sonnet 5.5	$0.00008	$0.00137
Haiku 4.5	$0.00004	$0.00068

Measured 25d ago against content hash 2d73d9a5585e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 25d 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.

skills/release/SKILL.md · 61 lines

How it starts

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

Release Cyrus

Run Cyrus releases through the trusted-publishing workflow. Do not publish workspace packages manually.

Required reference

Read apps/cli/RELEASING.md completely before taking release actions. Treat it as the canonical operator guide and scripts/release-packages.mjs as the canonical package list and dependency order.

Editing release workflows, scripts, installers, or release documentation does not invoke this release procedure. Validate those changes with targeted checks and the F1 applicability policy in skills/f1-test-drive/SKILL.md.

Workflow

Fetch origin/main, start from current main, and preserve unrelated local changes.
Prepare the release on a branch:
- Move both changelogs' Unreleased entries into the new version.
- Set the same version in every manifest printed by node scripts/release-packages.mjs list.
- Run pnpm install and commit any lockfile change.
- Assess the entire payload since the previous release using the canonical F1 applicability policy, including functional changes merged before the version-bump PR. For F1-covered behavior changes, run relevant F1 scenarios and save evidence with the required -release-v<version>.md suffix. Otherwise record the payload assessment and targeted checks as non-F1 release verification per apps/cli/RELEASING.md; do not invent an F1 report.
- List every released package@version in CHANGELOG.md.
Run node scripts/release-packages.mjs validate <version>, then all checks required by apps/cli/RELEASING.md. Fix failures before continuing.
Commit, push, open the release PR, and merge it to main before dispatching the workflow. Never publish unmerged source or a non-main ref.
Dispatch .github/workflows/release-cli.yml from main in dry-run mode and monitor it through completion.
Only when the user has explicitly requested the live release, dispatch the same exact version with dry_run=false. Monitor it through npm publication, git tagging, and GitHub Release creation.
Independently verify the version on npm and run the published CLI's --version command.
Use the Linear integration to move every issue referenced by the version's changelog section from MergedUnreleased to ReleasedMonitoring.

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

25d ago Changed · +8 lines 2d73d9a5585e
1mo ago First seen · 53 lines · 42 tokens per session scan A 831bd0741bce

Subscribe to this mod's changes

release is a skill published in the GitHub repository cyrusagents/cyrus (858 stars, last pushed 5d ago), licensed Apache-2.0. It adds 42 tokens to every session and 684 once invoked, about $0.0002 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-30.

Git and workflow Releases agent ai claude claudecode engineer linear

baby-sit

Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.

langchain-ai/open-swe · 30 tokens

release-announcement

A release-promotion tool that turns a project's latest Markdown release notes into a short WeChat group message and a vertical PNG poster. It checks GitHub contributor IDs and downloads their real public profile pictures; it does not create or publish a GitHub Release.

NanmiCoder/cc-haha · 56 tokens

release