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.
npx agentmods add skills/cyrusagents/cyrus/releasenpx skills add cyrusagents/cyrus --skill releasegit clone --depth 1 https://github.com/cyrusagents/cyrusWrote 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/cyrusagents/cyrus/release)<a href="https://agentmods.dev/skills/cyrusagents/cyrus/release"><img src="https://agentmods.dev/badge/skills/cyrusagents/cyrus/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 | $0.00042 | $0.00569 |
| Opus 5 | $0.00021 | $0.00284 |
| Sonnet 5 | $0.00008 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
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 4d 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 — 53 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.
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 installand commit any lockfile change. - Run the F1 release test-drive protocol and save its report with the
required
-release-v<version>.mdsuffix. - List every released
package@versioninCHANGELOG.md.
- Run
node scripts/release-packages.mjs validate <version>, then all checks required byapps/cli/RELEASING.md. Fix failures before continuing. - Commit, push, open the release PR, and merge it to
mainbefore dispatching the workflow. Never publish unmerged source or a non-main ref. - Dispatch
.github/workflows/release-cli.ymlfrommainin 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
--versioncommand. - Use the Linear integration to move every issue referenced by the version's
changelog section from
MergedUnreleasedtoReleasedMonitoring.
Safety
- Never add an npm token. Publishing must use GitHub Actions OIDC.
- Confirm every npm package trusts
cyrusagents/cyrusandrelease-cli.ymlbefore the first live workflow run. - A dry run does not authenticate to npm and does not prove registry writes.
- Never rerun a partially published version blindly. npm versions are immutable; inspect which packages landed and recover deliberately.
- Do not create or move a release tag until every package is published. The workflow owns tag and GitHub Release creation.
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.
- 4d ago First seen · 53 lines · 42 tokens per session scan A 831bd0741bce
release is a skill published in the GitHub repository cyrusagents/cyrus (792 stars, last pushed 5d ago), licensed Apache-2.0. It adds 42 tokens to every session and 569 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-30.
Other skills, from other repositories
Release Notes Generation
Mandatory fast-mcp-telegram release workflow. Use when the user says release, merge and release, bump version, tag, gh release, PyPI publish, or Telegram version announcement.
release-workflow
Use when creating a new release on main branch, tagging a version, or updating CHANGELOG before pushing a git tag.
changelog
Update CHANGELOG.md with user-facing changes. Use when the user wants to update the changelog, prepare for a release, or document what changed since the last version.
changelog
Changelog Generation Command 📝.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
continual-learning
Nightly refinement of an existing per-repo review-style prompt using this reviewer's own finding outcomes. Read confirmed (resolved-by-commit / thumbs-up) and dismissed (thumbs-down) findings, promote the bug patterns the team actually fixes, demote the false-positive patterns, reconcile against the current prompt…