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.
curl -O https://raw.githubusercontent.com/carloluisito/mindkeg-mcp/main/.claude/commands/release.mdgit clone --depth 1 https://github.com/carloluisito/mindkeg-mcpWrote 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.
[](https://agentmods.dev/commands/carloluisito/mindkeg-mcp/release)<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.
<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>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 | $0.00000 | $0.00531 |
| Sonnet 5 | $0.00000 | $0.00212 |
| Haiku 4.5 | $0.00000 | $0.00106 |
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 10d 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.
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.jsonto 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 --onelineto 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.mdand 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.mdarchitecture 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:→ Addedfix:→ Fixedrefactor:,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.
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.
- 10d ago First seen · 108 lines · 0 tokens per session scan A 2c944b679cc6
release is a command published in the GitHub repository carloluisito/mindkeg-mcp (11 stars, last pushed 4mo 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.
Other commands, from other repositories
bump-plugin
Bump changed plugin and marketplace version.
bump
Bump the app version or build number across all targets in the current project.
openspec-archive
Archive a deployed OpenSpec change and update specs.
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
get-unpublished-changes
Compare HEAD with the latest published npm versions and list all unpublished changes by release layer.