release

A release procedure for publishing Chamber builds through either an invite-only insiders channel or a public stable channel. Chamber is the software project whose builds are being distributed.

In plain words
What is it for?
Publishing builds to insiders, releasing stable versions publicly, sending builds to testers, and promoting a version to the public channel.
Why use it?
It provides the steps and destinations needed to make a build available to testers or the public. It also distinguishes releasing a build from shipping a code change such as a pull request.

Skill for Claude CodeCodex

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/ianphil/chamber/release
Any agent
npx skills add ianphil/chamber --skill release
Clone the repo
git clone --depth 1 https://github.com/ianphil/chamber

Made for: Claude Code, Codex.

Per session 139 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 6,923 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.

ModelPer sessionOnce invoked
Fable 5 $0.00139 $0.06923
Opus 5 $0.00069 $0.03461
Sonnet 5 $0.00028 $0.01385
Haiku 4.5 $0.00014 $0.00692

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

Security

Grade A, and why

release scanned grade A with 1 finding 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 2d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -fsSL https://chmbr.dev/flags/v1/flags.json
.github/skills/release/SKILL.md · 688 lines

How it starts

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

Release Skill

Dispatch a Chamber release. Two channels, picked deliberately, dispatched manually. Authoritative mechanics live in ai-docs/release-channels.md; this skill is the operational runbook on top of them.

This skill is not the same as ship. Ship lands PRs. Release publishes builds. Neither calls the other.

When to invoke

Trigger on any of these (or close variants):

  • "release", "release insiders", "release stable", "cut a release"
  • "ship a build" (when distinct from "ship a PR" — ask if unclear)
  • "publish", "publish stable", "publish to GitHub Releases"
  • "promote", "promote insiders", "promote to stable"
  • "make a build available to testers", "send to testers", "push to insiders"
  • "go public with this", "make this the public version"

If the user's intent is ambiguous between PR shipping and build shipping, ask once. If the channel is ambiguous, ask once.

Channels

Channel Audience Workflow Distribution Platforms
Insiders Invite-only .github/workflows/release-insiders.yml Azure Blob chamberinsiders Windows + macOS arm64 (signed + notarized)
Stable Public .github/workflows/release.yml GitHub Releases Windows + macOS arm64 (+x64 opt-in; macOS can be disabled by repo variable)

Both are workflow_dispatch only — neither fires on push.

The core shape to keep in mind:

  • Insiders cut = compute target stable from ## [Unreleased] in CHANGELOG.md → bump counter (vX.Y.Z-insiders.N) → build → upload to blob → push the tag only. Master is never modified.
  • Stable cut is almost always promote an insider tag (source_ref: vX.Y.Z-insiders.N). Direct-from-master dispatch is an emergency fallback that derives the version from ## [Unreleased] the same way insiders does.
  • Stable feature flags are controlled by the GitHub Pages policy at docs/flags/v1/flags.json. Stable releases must ask whether any preview flags are graduating to stable before dispatching the stable workflow.
  • Post-stable (this skill's responsibility, run locally): open a PR that bumps package.json to the freshly shipped stable version and promotes ## [Unreleased] into ## [X.Y.Z] - YYYY-MM-DD in CHANGELOG.md (Keep a Changelog 1.1.0 format). This keeps master's invariant (version = last shipped stable).

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

  1. 2d ago First seen · 688 lines · 139 tokens per session scan A 3b29f2637813

Subscribe to this mod's changes

release is a skill published in the GitHub repository ianphil/chamber (11 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 6,923 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

smoke-test

End-to-end smoke test skill for DeerFlow. Guides through: 1) Pulling latest code, 2) Docker OR Local installation and deployment (user preference, default to Local if Docker network issues), 3) Service availability verification, 4) Health check, 5) Final test report. Use when the user says "run smoke test", "smoke…

bytedance/deer-flow · 0 tokens

image-generation

Use this skill when the user requests to generate, create, imagine, or visualize images including characters, scenes, products, or any visual content. Supports structured prompts and reference images for guided generation.

bytedance/deer-flow · 42 tokens

podcast-generation

Use this skill when the user requests to generate, create, or produce podcasts from text content. Converts written content into a two-host conversational podcast audio format with natural dialogue.

bytedance/deer-flow · 38 tokens

vercel-deploy

Deploy applications and websites to Vercel. Use this skill when the user requests deployment actions such as "Deploy my app", "Deploy this to production", "Create a preview deployment", "Deploy and give me the link", or "Push this live". No authentication required - returns preview URL and claimable deployment link.

bytedance/deer-flow · 69 tokens

skill-reviewer

Reviews DeerFlow skill packages for readiness, triggers, safety boundaries, resources, and evidence. Invoke when users ask to audit, grade, or production-check an existing skill.

bytedance/deer-flow · 38 tokens

surprise-me

Create a delightful, unexpected "wow" experience for the user by dynamically discovering and creatively combining other enabled skills. Triggers when the user says "surprise me" or any request expressing a desire for an unexpected creative showcase. Also triggers when the user is bored, wants inspiration, or asks for…

bytedance/deer-flow · 67 tokens