A release-note file for recording what changed and which version number should increase. A changeset is commonly used by projects that publish packages or other versioned software.

Use it to inspect the current branch, choose a patch, minor, or major change, and create the required Markdown entry.

It keeps version bumps and changelog entries consistent instead of relying on memory when changes are released.

changeset — Skill by alchemyplatform

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/alchemyplatform/alchemy-mcp-server/changeset

Any agent

npx skills add alchemyplatform/alchemy-mcp-server --skill changeset

Clone the repo

git clone --depth 1 https://github.com/alchemyplatform/alchemy-mcp-server

Made for: Claude Code, Codex.

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

When invoked 296 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.00020	$0.00296
Opus 5	$0.00010	$0.00148
Sonnet 5	$0.00004	$0.00059
Haiku 4.5	$0.00002	$0.00030

Measured 2d ago against content hash 0a6d11236a44, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

changeset 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/changeset/SKILL.md · 30 lines

What it actually says

Create a changeset entry for the current branch's changes.

Instructions

Run git diff main...HEAD --stat and git log main..HEAD --oneline to understand what changed on this branch.
If no argument was provided, analyze the changes to determine:
- Bump type: patch for fixes, minor for new features, major for breaking changes
- Summary: A concise description of the change for the changelog
If $ARGUMENTS was provided, parse it as [bump] [description] (e.g., minor Add changeset-based release workflow).
Create a new markdown file in .changeset/ with a random lowercase-kebab-case name (e.g., .changeset/cool-birds-fly.md) using this exact format:

---
"@alchemy/mcp-server": <bump>
---

<description>

Where <bump> is patch, minor, or major and <description> is the changelog entry.

Show the user the created changeset file and ask if they'd like to adjust anything.

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 · 30 lines · 20 tokens per session scan A 0a6d11236a44

Subscribe to this mod's changes

changeset is a skill published in the GitHub repository alchemyplatform/alchemy-mcp-server (88 stars, last pushed 22d ago), licensed MIT. It adds 20 tokens to every session and 296 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

prepare-providers-documentation

Replace the manual commit-by-commit classification step in breeze release-management prepare-provider-documentation with AI-driven classification. For each provider with pending changes, analyze every PR (batched into one sub-agent per provider, not one per PR), pay special attention to potentially breaking changes by…

apache/airflow · 113 tokens

land-and-deploy

Land and deploy workflow. (gstack).

garrytan/gstack · 14 tokens

landing-report

Read-only queue dashboard for workspace-aware ship. (gstack).

garrytan/gstack · 16 tokens

flutter-cherry-pick

How to land a formal cherry-pick of a merged PR for the flutter/flutter repo stable or beta channel. Only use for flutter/flutter landed pull requests. Only use when the cherry pick request is into "stable", "beta" or a branch that has the format with flutter- . -candidate.0.

flutter/flutter · 72 tokens

version-bump

Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. NPM publishing is the final human-required handoff because the maintainer…

thedotmack/claude-mem · 64 tokens

release-changelog

Generate the stable Paperclip release changelog at releases/vYYYY.MDD.P.md by reading commits, changesets, and merged PR context since the last stable tag.

paperclipai/paperclip · 37 tokens