A release workflow for the mindkeg-mcp project, where a release is a published version of the software.

Use it to prepare releases using an explicit version or a patch, minor, or major version change. It also checks the project's README before release work continues.

It helps determine the next version, review changes since the last release, and check that user documentation matches those changes.

How carloluisito/mindkeg-mcp configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to carloluisito/mindkeg-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/carloluisito/mindkeg-mcp/main/.claude/commands/release.md

Clone the repo

git clone --depth 1 https://github.com/carloluisito/mindkeg-mcp

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/carloluisito/mindkeg-mcp/release/github.svg)](https://agentmods.dev/commands/carloluisito/mindkeg-mcp/release)

Your own site

<a href="https://agentmods.dev/commands/carloluisito/mindkeg-mcp/release"><img src="https://agentmods.dev/badge/commands/carloluisito/mindkeg-mcp/release/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/carloluisito/mindkeg-mcp/release"><img src="https://agentmods.dev/badge/commands/carloluisito/mindkeg-mcp/release.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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 1,061 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00000	$0.01061
Opus 5.5	$0.00000	$0.00424
Sonnet 5.5	$0.00000	$0.00212
Haiku 4.5	$0.00000	$0.00106

Measured 2mo ago against content hash 2c944b679cc6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 2mo 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 · 108 lines

How it starts

The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are performing a release for the mindkeg-mcp project. The user will provide the version as $ARGUMENTS (e.g., "0.2.0" or "patch" or "minor" or "major").

Follow these steps exactly:

1. Determine the new version

Read package.json to get the current version.
If the user provided a semver keyword ("patch", "minor", "major"), compute the next version:
- patch: 0.1.0 → 0.1.1
- minor: 0.1.0 → 0.2.0
- major: 0.1.0 → 1.0.0
If the user provided an explicit version (e.g., "0.2.0"), use that directly.
If no argument was provided, ask the user what version to release.

2. Collect changes since the last release

Run git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline to get all commits since the last tag.
If there are no commits since the last tag, stop and tell the user there's nothing to release.

3. Documentation check

Before proceeding, verify that user-facing documentation is up to date with the changes being released:

Read README.md and check that any new CLI commands, features, configuration options, or API changes from the commits in step 2 are documented.
Check that the CLI Commands section, Quick Start section, and Configuration table reflect the current state.
Check that CLAUDE.md architecture section is consistent with any structural changes.
If documentation is missing or outdated, update it now and include the changes in the release commit.
Tell the user what documentation updates you made (if any). If everything is already documented, say so.

4. Update CHANGELOG.md

Read the current CHANGELOG.md.
Add a new section at the top (below the header), formatted as:

## [X.Y.Z] - YYYY-MM-DD

### Added
- (new features from commit log)

### Changed
- (modifications from commit log)

### Fixed
- (bug fixes from commit log)

Only include sections (Added/Changed/Fixed) that have entries. Categorize commits by reading their messages:
- feat: → Added
- fix: → Fixed
- refactor:, perf:, docs:, ci:, chore: → Changed
Write concise, user-facing descriptions (not raw commit messages). Group related commits.
Today's date should be used for the release date.

Read the full file on GitHub · 108 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.

2mo ago First seen · 108 lines · 0 tokens per session scan A 2c944b679cc6

Subscribe to this mod's changes

release is a command published in the GitHub repository carloluisito/mindkeg-mcp (11 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,061 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-30.

Git and workflow Releases agent ai ai-tools claude cursor embeddings

release next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
releasecarloluisito/mindkeg-mcp	Command	11	6mo ago	MIT	A	0	Claude Code
bump-pluginNeoLabHQ/context-engineering-kit	Command	1.8k	2mo ago	GPL-3.0	A	7	Claude Code
bumpcarloshpdoc/ios-workflow-claude	Command	7	5mo ago	Apache-2.0	A	0	Claude Code
openspec-archiveAlenryuichi/openmemory-plus	Command	20	8mo ago	MIT	A	10	Claude Code
shipaddyosmani/agent-skills	Command	114k	5d ago	MIT	A	21	Claude Code
CHANGELOGbytedance/UI-TARS-desktop	Command	40k	29d ago	Apache-2.0	A	0	Claude Code
get-unpublished-changescode-yeongyu/oh-my-openagent	Command	71k	yesterday	none	A	16	OpenCode

mindkeg-mcp: Command for Claude Code