A release procedure for VibeFrame, including version changes, generated release files, checks, and a release commit. A patch, minor, or major version indicates the size and impact of the release.

It helps prepare VibeFrame releases, check release status, choose the version bump, regenerate artifacts, run validation, and enforce the rules for less common minor or major releases.

It provides a repeatable process for deciding what a release contains and prevents ordinary code changes from receiving unnecessary version bumps.

How vericontext/vibeframe configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to vericontext/vibeframe. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/vericontext/vibeframe/main/.agents/skills/release/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/vericontext/vibeframe

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/vericontext/vibeframe/release/github.svg)](https://agentmods.dev/skills/vericontext/vibeframe/release)

Your own site

<a href="https://agentmods.dev/skills/vericontext/vibeframe/release"><img src="https://agentmods.dev/badge/skills/vericontext/vibeframe/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/vericontext/vibeframe/release"><img src="https://agentmods.dev/badge/skills/vericontext/vibeframe/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.1	$0.00022	$0.01225
Opus 5.5	$0.00009	$0.00490
Sonnet 5.5	$0.00004	$0.00245
Haiku 4.5	$0.00002	$0.00122

Measured 21d ago against content hash ec0407c090b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 21d 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.

.agents/skills/release/SKILL.md · 152 lines

How it starts

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

Release

Use this skill when the user asks Codex to cut a VibeFrame release.

The bump is one of patch, minor, or major. Default to patch when no bump is specified or when there is any doubt.

When Bumps Happen

Once per release, not once per PR. Ordinary feat: / fix: PRs merge to main without a version bump. This skill runs when you decide to release, and the single bump it produces must cover every commit since the last tag - git-cliff handles that automatically in step 7.

Check what the release will cover before starting:

bash scripts/release-status.sh

That script is the single source of truth for release state. The push gate, the tag workflow, and the daily drift check all call it, so its answer is the same one CI will give.

Version Policy

VibeFrame is still in 0.x. patch is the default and by far the most common bump. minor is rare and must be explicitly justified — the shared push gate (scripts/pre-push-validate.sh) blocks a non-patch bump that lacks a Release-Type: trailer (see step 10).

patch: bug fixes, docs/tooling, UX polish, internal refactors, and most ordinary feat: / fix: commits. Use this unless a rule below clearly applies.
minor: new public CLI command namespace, new MCP tool family, public API contract additions, or a large product milestone.
major: breaking changes or an intentional 1.0 milestone.

When unsure, use patch.

Steps

Read the current root version:
```
jq -r '.version' package.json
```

Bump the root package:

npm version <patch|minor|major> --no-git-tag-version

Read the exact new version:

NEW_VERSION=$(jq -r '.version' package.json)

Set every workspace package to that exact version. Do not use pnpm -r exec npm version for this step because recursive pnpm includes the root package.

for dir in packages/cli packages/core packages/ai-providers packages/mcp-server apps/web; do
  (cd "$dir" && npm version "$NEW_VERSION" --no-git-tag-version)
done

Read the full file on GitHub · 152 lines

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.

21d ago Changed ec0407c090b4
2mo ago First seen · 152 lines · 22 tokens per session scan A f407ae48eb34

Subscribe to this mod's changes

release is a skill published in the GitHub repository vericontext/vibeframe (185 stars, last pushed yesterday), licensed MIT. It adds 22 tokens to every session and 1,225 once invoked, about $0.0001 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-08-30.

Git and workflow Releases ai ai-agents claude cli developer-tools ffmpeg

release next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releasevericontext/vibeframe	Skill	185	yesterday	MIT	A	22	Claude Code, Codex
rea-changelog-updatemorluto/rea	Skill	435k	yesterday	MIT	A	33	Claude Code
codew-release-qa-sweepHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	31	Claude Code, Codex
releaseHmbown/CodeWhale	Skill	41k	5d ago	MIT	A	0	Claude Code, Codex
skillshare-releaserunkids/skillshare	Skill	2.9k	yesterday	MIT	A	77	Claude Code
skillshare-changelogrunkids/skillshare	Skill	2.9k	yesterday	MIT	A	134	Claude Code
githubAtomicBot-ai/atomic-agent	Skill	3.4k	8d ago	MIT	A	48	Claude Code, Codex

vibeframe: Skill for Claude Code