What is version-plans?

A guide for creating a version plan, which records the release-version change and user-facing summary for a publishable package. It explains when plans are required and how workspace packages are versioned.

Use it when changing the behavior of a publishable package, generating a Changeset, checking package names, or validating release plans.

It prevents unnecessary plans for documentation-only or excluded changes and helps ensure package releases use the correct version bump.

version-plans — Agent by callstackincubator

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 agents/callstackincubator/rozenite/version-plans

Clone the repo

git clone --depth 1 https://github.com/callstackincubator/rozenite

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 335 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00335
Opus 5	$0.00000	$0.00168
Sonnet 5	$0.00000	$0.00067
Haiku 4.5	$0.00000	$0.00034

Measured today against content hash 7cce583e0853, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

version-plans 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 today.

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.

docs/agents/version-plans.md · 49 lines

What it actually says

Version plans

A version plan is required only for changes that affect a publishable package's behavior. Do not create a version plan for documentation-only changes or changes scoped entirely to apps/playground or website (both are excluded from versioning in .changeset/config.json).

Create the plan

Generate the Changeset interactively:
```
pnpm changeset
```
Follow the prompts to select the affected packages and the appropriate version bump. Note that all @rozenite/* packages are pinned together (see the fixed field in .changeset/config.json), so picking any one of them bumps them all in lockstep.
Review the generated Markdown file under .changeset/. Package names must exactly match their workspace package.json names.
Write a concise, user-facing summary after the frontmatter. Describe the capability, behavior, or fix—not the files or implementation technique.

Examples

---
'@rozenite/ui': minor
---

Add new `@rozenite/ui` package — shared UI primitives and plugin layout
components built on HeroUI and Tailwind CSS.

Check the plan

Run the following to confirm the branch contains a Changeset relative to main:

pnpm release:plan

This is the same check CI runs and will fail the build if a version plan is missing for a relevant change. Existing files in .changeset/ are the repository's best examples for tone and release scope.

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.

today First seen · 49 lines · 0 tokens per session scan A 7cce583e0853

Subscribe to this mod's changes

version-plans is an agent published in the GitHub repository callstackincubator/rozenite (653 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 335 tokens. 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.

Frontend Git and workflow Writing and docs devtools react-native

debugger

Debugs errors, test failures, and unexpected behavior. Knows PromptScript architecture.

mrwogu/promptscript · 20 tokens

worktree-collaboration

This document defines the default collaboration protocol for multiple Agents working on Vibelution in parallel.

CCDawn/Vibelution · 0 tokens

sdd-tester

Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.

chohra-med/expo_boilerplate · 61 tokens

version-plans