A release-preparation procedure for increasing Plano’s version number across its required source, configuration, documentation, and workflow files.

Use it when preparing a major, minor, or patch release and updating the dependency lock data afterward.

It reduces the chance of leaving different files on different versions or accidentally changing protected lock files.

release — Skill by katanemo

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/katanemo/plano/release

Any agent

npx skills add katanemo/plano --skill release

Clone the repo

git clone --depth 1 https://github.com/katanemo/plano

Made for: Claude Code, Codex.

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

When invoked 324 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.00018	$0.00324
Opus 5	$0.00009	$0.00162
Sonnet 5	$0.00004	$0.00065
Haiku 4.5	$0.00002	$0.00032

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

.claude/skills/release/SKILL.md · 31 lines

What it actually says

Prepare a release version bump. The user may provide the new version number as $ARGUMENTS (e.g., /release 0.4.12), or a bump type (major, minor, patch).

If no argument is provided, read the current version from cli/planoai/__init__.py, auto-increment the patch version (e.g., 0.4.11 → 0.4.12), and confirm with the user before proceeding.

Update the version string in ALL of these files:

.github/workflows/ci.yml
cli/planoai/__init__.py
cli/planoai/consts.py
cli/pyproject.toml
build_filter_image.sh
config/validate_plano_config.sh
docs/source/conf.py
docs/source/get_started/quickstart.rst
docs/source/resources/deployment.rst
apps/www/src/components/Hero.tsx
demos/llm_routing/preference_based_routing/README.md

Do NOT change version strings in *.lock files or Cargo.lock.

After updating all version strings, run cd cli && uv lock to update the lock file with the new version.

After making changes, show a summary of all files modified and the old → new version.

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.

2d ago First seen · 31 lines · 18 tokens per session scan A b1cd834daab3

Subscribe to this mod's changes

release is a skill published in the GitHub repository katanemo/plano (7,033 stars, last pushed 13d ago), licensed Apache-2.0. It adds 18 tokens to every session and 324 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.

Git and workflow Releases gateway generative-ai llm-inference llms prompt proxy

changelog-writer

Write changelogs for Bifrost releases. Reads git history, bumps module versions following the core→framework→plugins→transport hierarchy, writes transports/changelog.md (enterprise-style) and per-module changelog.md files, and updates version files. Invoked with /changelog-writer or /changelog-writer .

maximhq/bifrost · 73 tokens

release-checklist

Pre-release safety audit for the Bifrost repo. Scans database migrations changed in a release for high-scale deadlock / lock-contention risks and for work that blocks application boot time, then produces a pass/warn/fail report with a concrete remediation plan. Invoked with /release-checklist [git-ref-range]. Built to…

maximhq/bifrost · 82 tokens

ship-release

Drive a Telepresence release from a prepared branch all the way through CI, docs, the Releases workflow, and PR merges. Assumes make prepare-release has already been run locally and the branch with that commit was pushed and a PR opened. Use when the user says "ship the release", or "complete the release". User-only.

telepresenceio/telepresence · 72 tokens

changelog-entry

Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".

telepresenceio/telepresence · 60 tokens

prepare-release

Create the local release commit and tags by setting TELEPRESENCEVERSION and running make prepare-release. Stops at the local commit+tags - pushing is the ship-release skill's job. Use when the user explicitly asks to prepare a release, RC, or test build. User-only.