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 skills add virgoC0der/awesome-claude-code --skill channels-releasegit clone --depth 1 https://github.com/virgoC0der/awesome-claude-codeWrote 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/virgoc0der/awesome-claude-code/channels-release)<a href="https://agentmods.dev/skills/virgoc0der/awesome-claude-code/channels-release"><img src="https://agentmods.dev/badge/skills/virgoc0der/awesome-claude-code/channels-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/virgoc0der/awesome-claude-code/channels-release"><img src="https://agentmods.dev/badge/skills/virgoc0der/awesome-claude-code/channels-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.00063 | $0.02027 |
| Opus 5.5 | $0.00025 | $0.00811 |
| Sonnet 5.5 | $0.00013 | $0.00405 |
| Haiku 4.5 | $0.00006 | $0.00203 |
Grade A, and why
channels-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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Channels Release
Create a normal release ticket from live CMDB, Release Train, and App Center data. Preserve the user's exact service, environment, and version scope. Creating a draft, publishing a ticket, and completing an actual deployment are separate outcomes.
Read references/profiles.md after the requested domain or service is known. Use its product and checklist mappings as exact-match hints, not as authority over live data.
Hard boundaries
- This workflow is for
releaseonly. Route hotfix, rollback, and restart requests to the genericrt-create-ticketskill. - Never add production because a tag is a release tag or because a prior ticket included production. Only an explicit user request authorizes a production task.
- A staging-only request must produce only staging deploy and staging rollback tasks. After creation and publication, require
has_production_env=falseon readback. - Do not infer a product from a service name.
prod-af-mcp-serverbelongs toAfterShip Feed, notAfterShip Affiliates. - Never fuzzy-match a service, environment, artifact, product, or checklist. A missing or ambiguous exact match is blocking.
- Do not claim a service is deployed merely because the Release Train ticket was published. Confirm an App Center publish record for the ticket/task and wait for
status=success.
Preflight
Run:
which clime
clime release-train version
clime app-center version
clime release-train auth status --output json
clime app-center auth status -O json
Require release-train >= 1.0.3 and app-center >= 1.1.0. Older App Center versions can accept -r but fail artifact queries with ListArtifactsInput.CIName ... required; the working artifact selector is -c <ci-name>.
If a CLI is missing, outdated, or logged out, stop and tell the user. Do not install, replace, update, or log in without their approval. The current official manifest is https://files.am-usercontent.org/AfterShip-CLI/common/plugins.yaml; do not silently reuse obsolete .me/.../common/install.sh sources.
What ships with it
2 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.
- 1mo ago First seen · 177 lines · 63 tokens per session scan A 70065bce8b5f
channels-release is a skill published in the GitHub repository virgoC0der/awesome-claude-code (1 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 2,027 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-09-12.
Other skills, from other repositories
xberg-release
Xberg release on top of the shared release-workflow: task version:sync to bindings and chart, CI/Publish/Benchmarks readiness. Use before a release.
factory-ship
Experimental workflow for publishing and completing configured software delivery work. Use when the user or an enabled factory policy asks to ship.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
seed-snapshot-release
An automated workflow for creating and tracking a snapshot release of the pull request on the current branch. A snapshot release is a temporary package build used for testing a branch before a normal release.
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
cmux-release
Prefer the /release command. It determines the new version (minor by default), gathers the Changelog line from each PR merged since the last stable tag, updates CHANGELOG.md, runs ./scripts/bump-version.sh, commits, runs ./scripts/release-pretag-guard.sh, then tags and pushes.