Borrowing it
Nothing to install: this file belongs to ianphil/chamber. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ianphil/chamber/master/.github/skills/release/SKILL.mdgit clone --depth 1 https://github.com/ianphil/chamberWrote 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/ianphil/chamber/release)<a href="https://agentmods.dev/skills/ianphil/chamber/release"><img src="https://agentmods.dev/badge/skills/ianphil/chamber/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/ianphil/chamber/release"><img src="https://agentmods.dev/badge/skills/ianphil/chamber/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 106 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium MCP Rug Pull · line 340 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 341 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Rogue Agent · line 539 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00139 | $0.06959 |
| Opus 5.5 | $0.00056 | $0.02784 |
| Sonnet 5.5 | $0.00028 | $0.01392 |
| Haiku 4.5 | $0.00014 | $0.00696 |
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 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.
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 How it starts
The opening of the file, as written. The whole thing — 690 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; Linux x64 preview |
| 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]inCHANGELOG.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.jsonto the freshly shipped stable version and promotes## [Unreleased]into## [X.Y.Z] - YYYY-MM-DDinCHANGELOG.md(Keep a Changelog 1.1.0 format). This keeps master's invariant (version = last shipped stable).
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 Changed · +2 lines 129e0de44ba6
- 2mo ago First seen · 688 lines · 139 tokens per session scan A 3b29f2637813
release is a skill published in the GitHub repository ianphil/chamber (12 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 6,959 once invoked, about $0.0006 per session on Opus 5.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.
Other skills, from other repositories
release-cut
Cut a new pi-agent-dashboard release: promote ## [Unreleased] in CHANGELOG.md, bump every workspace package.json per SemVer, commit, tag v , and push — triggering the Release workflow that publishes every non-private workspace, builds the Electron artifacts, and creates a GitHub Release. Use on "cut a release"…
release-revoke
Revoke or rollback a pi-agent-dashboard release: delete the GitHub Release, remove the git tag locally and on origin, deprecate the npm version (npm unpublish is blocked after 72h), and optionally revert the release commit. Use when the user says "revoke release", "rollback release", "delete release", "unpublish…
03-release-tag
Cut a semver release with an annotated tag and release notes. Use when the user wants to release, tag a release, bump the version, or cut a version. Not for a plain commit, a pull request, or amending an existing tag.
ship-change
Ship an OpenSpec change after openspec-apply completes. When only QA/manual tasks remain, marks them done (tested later), archives + syncs specs, commits, pushes, opens a PR against develop, watches CI, waits for CodeRabbit, auto-applies safe fixes and re-pushes, loops until CI green + no actionable review threads…
prime-silo-devops
DevOps, SDLC, Tagging, and Release management instructions for Prime-Silo. Use this when asked to tag a new release, check CI/CD build status, or manage the SDLC.
akiship
Full release ritual end-to-end — front-loaded checks, then an unattended pass. ACTIVATION = the literal token /akiship, or an imperative turn, in any language, ordering the release ritual for this repo. A question about it, or a completion word with no release object, activates nothing — consult the checklist and…