release

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.

In plain words
What is it for?
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.
Why use it?
It provides a repeatable process for deciding what a release contains and prevents ordinary code changes from receiving unnecessary version bumps.

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

Made for: Claude Code, Codex.

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,227 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.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.01227
Opus 5 $0.00011 $0.00613
Sonnet 5 $0.00004 $0.00245
Haiku 4.5 $0.00002 $0.00123

Measured 2d ago against content hash f407ae48eb34, 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 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 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.

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

  1. Read the current root version:

    jq -r '.version' package.json
    
  2. Bump the root package:

    npm version <patch|minor|major> --no-git-tag-version
    
  3. Read the exact new version:

    NEW_VERSION=$(jq -r '.version' package.json)
    
  4. 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 packages/ui 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.

  1. 2d 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 (165 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 1,227 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

pr-to-video

Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR…

heygen-com/hyperframes · 104 tokens

slideshow

Author a HyperFrames slideshow — a presentation, pitch deck, or interactive deck with discrete slides, fragment reveals, branching, hotspot navigation, and built-in presenter mode with speaker notes; also converts an existing page into a deck. Output is a navigable deck, not a rendered MP4. If the user didn't…

heygen-com/hyperframes · 83 tokens

faceless-explainer

Turn arbitrary text — an article, notes, a topic, a brief — into a faceless explainer video: there is no site or footage to capture, so the visuals are invented per scene (typography, abstract graphics, diagrams, data-viz). Use for topic explainers, concept breakdowns, how-tos, listicles. Not a video built from a…

heygen-com/hyperframes · 98 tokens

figma

Import Figma content into a HyperFrames composition — rendered assets, brand tokens, components, storyboard sections → reconstructed motion (frames read as states, not slides) (REST/CLI), connector-assisted motion when available, and shaders from a connector or native export. Use when the user pastes a figma.com link…

heygen-com/hyperframes · 89 tokens

general-video

Author or edit a custom HyperFrames composition when no specialized workflow fits, or when BRIEF.md sets flow: companion. Use for longer or multi-scene pieces, brand and sizzle reels, montages, static loops, static title cards, footage remixes, and freeform builds. Use motion-graphics instead for a short unnarrated…

heygen-com/hyperframes · 92 tokens

motion-graphics

A short, design-led motion graphic where motion is the message — kinetic typography, stat count-up, chart/data-viz hit, logo sting / brand lockup, lower-third / callout / social overlay, animated map (highlight regions, connect places, zoom to a location), animated tweet / news-article / headline, webpage / UI…

heygen-com/hyperframes · 139 tokens