Borrowing it
Nothing to install: this file belongs to Agent-Clubhouse/Clubhouse-Workshop. 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/Agent-Clubhouse/Clubhouse-Workshop/main/.claude/skills/prepare-beta/SKILL.mdgit clone --depth 1 https://github.com/Agent-Clubhouse/Clubhouse-WorkshopWrote 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/agent-clubhouse/clubhouse-workshop/prepare-beta)<a href="https://agentmods.dev/skills/agent-clubhouse/clubhouse-workshop/prepare-beta"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/prepare-beta/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/agent-clubhouse/clubhouse-workshop/prepare-beta"><img src="https://agentmods.dev/badge/skills/agent-clubhouse/clubhouse-workshop/prepare-beta.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.00043 | $0.01698 |
| Opus 5 | $0.00022 | $0.00849 |
| Sonnet 5 | $0.00009 | $0.00340 |
| Haiku 4.5 | $0.00004 | $0.00170 |
Grade A, and why
prepare-beta 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 11d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare a Plugin Beta Release
This skill prepares a beta release for a single Workshop plugin using a 6-phase flow. The user provides the plugin ID as $ARGUMENTS. If omitted, list available plugins and ask.
Scope: All work is filtered to plugins/<plugin-id>/ — only commits touching that directory are considered.
Phase 1: Gather Data
# Ensure main is up to date
git checkout main && git pull origin main
# Read current version from manifest
cat plugins/<plugin-id>/manifest.json | grep '"version"'
# Find existing tags for this plugin
git tag --list '<plugin-id>-v*' --sort=-v:refname | head -10
# Determine last stable tag (no -beta in name) and last beta tag
LAST_STABLE=$(git tag --list '<plugin-id>-v*' --sort=-v:refname | grep -v '\-beta\.' | head -1)
LAST_BETA=$(git tag --list '<plugin-id>-v*-beta.*' --sort=-v:refname | head -1)
# Collect commits since last tag (stable or beta, whichever is newer)
# Use the newer of the two as the base
git log <last-tag>..HEAD --oneline --no-merges -- plugins/<plugin-id>/
If no previous tags exist for this plugin, collect all commits touching plugins/<plugin-id>/.
Determine beta increment: if LAST_BETA exists and is newer than LAST_STABLE, increment its beta number. Otherwise, start at -beta.1.
Phase 2: Classify Commits
Classify each commit using first-match-wins:
- Feature —
feat:prefix, or clearly new user-visible functionality - Bug Fix —
fix:prefix, or user-visible bug correction - Internal —
perf:prefix, optimizations, performance improvements - Non-User —
chore:,ci:,test:,docs:,build:,refactor:
Skip version bump commits entirely (chore: bump version to ...).
Phase 3: Coalesce
- A Feature absorbs closely related fixes (show final state only)
- Multiple fixes in the same area → one entry
- Keep distinct items separate
- Drop all Non-User items completely — they never appear in release notes or PR body
- Internal items appear only as "Improvements" in the PR body (not in the title)
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.
- 11d ago First seen · 186 lines · 43 tokens per session scan A b7fc55eadade
prepare-beta is a skill published in the GitHub repository Agent-Clubhouse/Clubhouse-Workshop (2 stars, last pushed 3mo ago), licensed MIT. It adds 43 tokens to every session and 1,698 once invoked, about $0.0002 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-31.
Other skills, from other repositories
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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
updater_guide
Guidance for checking for and installing Row-Bot updates.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".