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/kryptobaseddev/cleo/ct-release-orchestratornpx skills add kryptobaseddev/cleo --skill ct-release-orchestratorgit clone --depth 1 https://github.com/kryptobaseddev/cleoWrote 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/kryptobaseddev/cleo/ct-release-orchestrator)<a href="https://agentmods.dev/skills/kryptobaseddev/cleo/ct-release-orchestrator"><img src="https://agentmods.dev/badge/skills/kryptobaseddev/cleo/ct-release-orchestrator.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.00131 | $0.02344 |
| Opus 5 | $0.00066 | $0.01172 |
| Sonnet 5 | $0.00026 | $0.00469 |
| Haiku 4.5 | $0.00013 | $0.00234 |
Grade A, and why
ct-release-orchestrator 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Orchestrator
Overview
Owns the canonical 4-verb release pipeline established by SPEC-T9345 and finalised when T9540 deleted the legacy start / verify / publish verbs (and the 12-step releaseShip monolith) plus T10103 deleted the deprecated ship shim. The current verb surface is documented in docs/release/verb-matrix.md — that file is the SSoT for verb-to-state mapping. This skill is the agent-facing entry point and references the matrix instead of redefining it.
Core Principle
Each verb owns exactly one state transition. No verb performs more than one mutation. Multi-step orchestration uses
ship-e2e-smoke(validator) — never compose the verbs into a custom script.
Canonical Pipeline
| Step | Verb / Workflow | Owns transition | Notes |
|---|---|---|---|
| 1 | cleo release plan <ver> --epic <id> |
(none) → planned |
Builds the Release Plan envelope; auto-writes CHANGELOG.md (T10105 closes the silent-skip gap) |
| 2 | cleo release open <ver> |
planned → pr-opened |
Dispatches release-prepare.yml; the workflow cuts the branch + opens the PR |
| 3 | (GHA) release-prepare.yml → PR merge |
pr-opened → pr-merged |
Owned by CI; verify via cleo release pr-status <ver> |
| 4 | (GHA) auto-tag-on-release-merge.yml (T10104) |
pr-merged → tag-pushed |
Auto-tag on merge — no manual git tag needed |
| 5 | cleo release reconcile <ver> |
tag-pushed → published |
Backfills 11 provenance tables; idempotent |
Optional validators (read-only / dry-run):
| Verb | Use |
|---|---|
cleo release ship-e2e-smoke <ver> --epic <id> |
One-shot end-to-end smoke. Dry-run by default; --execute performs real mutations. T10103. |
cleo release pr-status <ver> |
Poll release PR CI checks while waiting |
cleo release list / show <ver> |
Read-only inspection |
Immutable Constraints
| ID | Rule | Enforcement |
|---|---|---|
| RLSE-001 | Version MUST be CalVer (YYYY.MM.patch) per ADR-065 — never SemVer. |
cleo release plan rejects non-CalVer; exit 53. |
| RLSE-002 | CHANGELOG.md MUST be updated before the tag — always-write is the default behaviour of cleo release plan (T9784 deleted the manual changelog verb). |
Plan envelope refuses to advance to pr-opened if the changeset directory is unparseable (T10105). |
| RLSE-003 | All per-task evidence gates MUST be recorded via cleo verify <task> --gate <g> --evidence … BEFORE cleo complete. The legacy cleo release verify batch verb was deleted in T9540. |
ADR-051 per-task evidence ritual. |
| RLSE-004 | The release MUST be tagged via the auto-tag GHA workflow — not a manual git tag. |
T10104 closes the auto-tag gap. |
| RLSE-005 | Direct pushes to main are prohibited. Every release ships via a PR cut by release-prepare.yml. |
ADR-065 + branch protection (see docs/release/branch-protection-setup.md). |
| RLSE-006 | Version MUST be consistent across all workspace targets resolved by resolveVersionBumpTargets (root package.json + every workspace package + Cargo workspace). |
Version-bump preflight in release-prepare.yml. |
| RLSE-007 | Provenance reconcile MUST run within the release-publish workflow — never as a manual followup. | Invoked by release-publish.yml. |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 142 lines · 131 tokens per session scan A 476b3fbf2ee2
ct-release-orchestrator is a skill published in the GitHub repository kryptobaseddev/cleo (160 stars, last pushed 15d ago), licensed MIT. It adds 131 tokens to every session and 2,344 once invoked, about $0.0007 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-09-03.
Other skills, from other repositories
ship
Ship workflow: detect + merge base branch, run tests, review diff, bump VERSION, update CHANGELOG, commit, push, create PR. (gstack).
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
tutti-app-release
Set up, review, run, or debug external repositories that publish a Tutti workspace app through the reusable Tutti App Release GitHub Actions workflow. Use for caller workflows, tutti.app.json manifests, @tutti-os/app-release-tools, S3/CloudFront release hosting, latest.json, versions.json, catalog.json, catalog-only…
harness-release
Generic release automation for projects using Keep a Changelog + GitHub. Single confirmation gate then end-to-end automation: bump detection, CHANGELOG promotion, PR/main merge, tag, GitHub Release. Trigger: release, version bump, publish. Do NOT load for: implementation, review, planning, setup.
publish
Publish the Octop Python package: cut a release branch from develop, bump version, update CHANGELOG, open a PR to main; after merge, Actions tag on main (PyPI / Docker Hub + GHCR) and sync main into develop. Use when the user asks to publish, release, bump version, cut a release, or run /publish.