agentmods.dev

release

A release helper that guides you through creating a Changeset, a small file describing how a code change should affect package versions.

In plain words
What is it for?
Use it when preparing a release from the current Git branch, especially in a project containing the @mcify/core, @mcify/runtime, or @mcify/cli packages.
Why use it?
It removes the guesswork from checking changed packages, choosing patch, minor, or major version updates, and recording the user-visible reason.

Command for Claude Code

2 2mo ago A scan 15 tokens original Apache-2.0
View the source file Lelemon-studio/mcify
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 commands/lelemon-studio/mcify/release
Clone the repo
git clone --depth 1 https://github.com/Lelemon-studio/mcify

Made for: Claude Code.

Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 383 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.00015 $0.00383
Opus 5 $0.00008 $0.00192
Sonnet 5 $0.00003 $0.00077
Haiku 4.5 $0.00002 $0.00038

Measured 2d ago against content hash 26480056e940, 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/commands/release.md · 34 lines

What it actually says

Help the user declare a release for the changes on the current branch.

  1. Read git status and git diff main..HEAD --stat to see what changed.

  2. Identify which @mcify/* packages are affected:

    • packages/core/** → @mcify/core
    • packages/runtime/** → @mcify/runtime
    • packages/cli/** → @mcify/cli
    • Cross-package or workspace-only changes might not need a changeset (build config, tests, docs, ADRs, GitHub workflows).

  3. For each affected package, decide the bump:

    • patch — bug fix, no API change, no behavior surprises.
    • minor — new feature, additive API, backwards-compatible.
    • major — breaking change. (Until V1 ships, we should only bump minor under the alpha pre-release tag — the alpha workflow keeps users opt-in via @alpha dist-tag.)

  4. Write a 1–3 sentence summary in present tense, focused on the why and the user-visible impact.

  5. Create .changeset/<descriptive-slug>.md with this format:

    ---
'@mcify/<package>': <patch|minor|major>
---

<summary>

    For multiple packages, list each on its own frontmatter line.

  6. Stage the changeset file and commit it with chore(release): add changeset for <slug>.

  7. Stop before pushing or publishing. The user pushes; CI handles versioning and publishing via changesets/action.

Read .changeset/README.md if any of the above is unclear.

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 · 34 lines · 15 tokens per session scan A 26480056e940

Subscribe to this mod's changes

release is a command published in the GitHub repository Lelemon-studio/mcify (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 383 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-31.

Git and workflowReleases
Related

Other commands, from other repositories

review-renovate

Review and merge renovate PRs with automerge configuration updates.

liam-hq/liam · 11 tokens

push-and-release

Git pull, resolve conflicts, push, fix hook errors, then release.

nimbalyst/nimbalyst · 14 tokens

release

Perform a full release: generate release notes, bump version, commit, tag, and push.

elirantutia/vibeyard · 0 tokens

release

Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.

swingerman/ha-dual-smart-thermostat · 29 tokens

SHIP_RELEASE

Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.

Osiris-DevWorks/smart-citizen · 34 tokens

release

The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.

azrtydxb/procoder · 30 tokens