What is cc-switch-release?

Release instructions for a cc-switch fork, covering version updates, release commits, Git tags, pushes, and checking GitHub Actions and Releases. They distinguish the web release from the desktop release and identify the official repository.

Synchronizing versions, preparing releases, creating tags, optionally pushing them, and verifying web release builds and GitHub artifacts.

Release files, tags, and build workflows must stay aligned for the published artifact to use the intended version. The guide also prevents checking or publishing against the wrong repository.

cc-switch-release — Skill for Claude Code and Codex by cp-yu: Release instructions for a cc-switch fork, covering version updates…

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.

agentmods

npx agentmods add skills/cp-yu/cc-switch-web/cc-switch-release

Any agent

npx skills add cp-yu/cc-switch-web --skill cc-switch-release

Clone the repo

git clone --depth 1 https://github.com/cp-yu/cc-switch-web

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/cp-yu/cc-switch-web/cc-switch-release.svg)](https://agentmods.dev/skills/cp-yu/cc-switch-web/cc-switch-release)

Your own site

<a href="https://agentmods.dev/skills/cp-yu/cc-switch-web/cc-switch-release"><img src="https://agentmods.dev/badge/skills/cp-yu/cc-switch-web/cc-switch-release.svg" alt="Measured on agentmods" height="20"></a>

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 649 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00070	$0.00649
Opus 5	$0.00035	$0.00324
Sonnet 5	$0.00014	$0.00130
Haiku 4.5	$0.00007	$0.00065

Measured 5d ago against content hash b645597abcd0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cc-switch-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 5d 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/cc-switch-release/SKILL.md · 53 lines

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.

CC Switch Release

Use this skill for repo-specific release work in cc-switch.

Core Rules

Treat origin as the release repo: cp-yu/cc-switch-web.
Treat upstream as the source mirror. Do not use it for release verification unless the user explicitly asks.
Pass -R cp-yu/cc-switch-web to gh when checking Actions or Releases. The default gh repo may point elsewhere.
Treat official GitHub Releases as Web-only. Build Web Release runs on tag push. Desktop Release (Manual) is manual only.
Keep version fields aligned in:
- package.json
- src-tauri/Cargo.toml
- src-tauri/tauri.conf.json
Prefer scripts/release-manager.mjs over hand-editing version files when the task is version sync or release cutting.

Standard Workflow

Inspect repo state first. Run git status --short --branch, git log --oneline --decorate -5, and if needed read references/release-facts.md.
Decide the operation. Use sync when the user only wants version fields updated. Use release when the user wants commit + tag + optional push.
Preserve user intent in the index. Do not auto-stage unrelated files. If releasing, require the intended code changes to be staged before calling the release tool.
Run the repo helper. Version sync only: pnpm release:sync-version -- <version> Full release: pnpm release:cut -- <version> --push
Verify the result. Confirm git status is clean, HEAD/tag moved as expected, and version values match. For remote verification, use: gh -R cp-yu/cc-switch-web run list --limit 5 gh -R cp-yu/cc-switch-web release view v<version> --json tagName,name,publishedAt,url,assets

Failure Handling

If release-manager.mjs rejects the worktree, fix staging hygiene instead of bypassing the check.
If a tag already exists remotely, do not rewrite it unless the user explicitly asks for destructive history changes.
If Actions succeeded but a release is missing, verify the run and release against cp-yu/cc-switch-web, not the upstream repo.
If the task involves changing release behavior itself, edit the workflow or helper script first, then cut a new tag.

Read the full file on GitHub · 53 lines

Files

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.

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.

5d ago First seen · 53 lines · 70 tokens per session scan A b645597abcd0

Subscribe to this mod's changes

cc-switch-release is a skill published in the GitHub repository cp-yu/cc-switch-web (42 stars, last pushed 1mo ago), licensed MIT. It adds 70 tokens to every session and 649 once invoked, about $0.0003 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.

Git and workflow Releases

agent-release-swarm

Agent skill for release-swarm - invoke with $agent-release-swarm.

ruvnet/ruflo · 19 tokens

release-announcement

Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.

paperclipai/paperclip · 42 tokens

release

Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.

openai/symphony · 42 tokens

changelog

Create changelog files for important commits in a PR.

pipecat-ai/pipecat · 13 tokens

multi-agent-release-manager

Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.

chromium/chromium · 27 tokens

refresh-arm-sdk-release

WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…

Azure/azure-sdk-for-net · 91 tokens