release

release is a command for Claude Code from synaptiai/synapti-marketplace. It costs 27 tokens per session (2,128 once invoked), scanned A, original, Apache-2.0.

A release command that determines a semantic version and creates a changelog from merged pull requests. Semantic versioning uses version numbers to indicate the kind of change being released.

In plain words
What is it for?
Use it to prepare a versioned software release, review merged changes, generate release notes, and publish after confirmation.
Why use it?
It gathers the changes since the previous release and requires a person to confirm the release before publishing it.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: names the AskUserQuestion tool.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the flow plugin — 31 skills, 21 commands, 9 agents shipped together

Good fit Use it to prepare a versioned software release, review merged changes, generate release notes, and publish after confirmation.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add synaptiai/synapti-marketplace
Claude Code
/plugin install flow

Made for: Claude Code.

Or install flow, the plugin that ships this one along with the rest of its 31 skills, 21 commands, 9 agents.

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.

agentmods badge for release

README.md
[![agentmods](https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/release.svg)](https://agentmods.dev/commands/synaptiai/synapti-marketplace/release)
Your own site
<a href="https://agentmods.dev/commands/synaptiai/synapti-marketplace/release"><img src="https://agentmods.dev/badge/commands/synaptiai/synapti-marketplace/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,128 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00027 $0.02128
Opus 5 $0.00014 $0.01064
Sonnet 5 $0.00005 $0.00426
Haiku 4.5 $0.00003 $0.00213

Measured 4d ago against content hash 58d1a3b633e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-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 4d 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.

plugins/flow/commands/release.md · 187 lines

How it starts

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

Create Release v$ARGUMENTS

Tier 3 operation — always requires human confirmation.

Required Skills

  • merge-and-release — version calculation, changelog generation

Phase 1: Gather Context

Phase 2 version calculation and Phase 4 publish steps stay inline (they depend on $ARGUMENTS classification and user confirmation).

# Output: `###`-headed sections + KEY=value per
# `references/command-output-format.md`.

echo "### Current Version"
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "none")
echo "LAST_TAG=$LAST_TAG"
echo "TAG_PREFIX=v"   # default; settings.release.tagPrefix may override at Phase 2

echo ""
echo "### Merged PRs Since Last Release"
if [ "$LAST_TAG" != "none" ]; then
  SINCE=$(git log -1 --format=%aI "$LAST_TAG" 2>/dev/null)
  MERGED_JSON=$(gh pr list --state merged --search "merged:>=$SINCE" --json number,title,labels --limit 50 2>/dev/null); GH_EXIT=$?
  echo "SINCE=$SINCE"
else
  MERGED_JSON=$(gh pr list --state merged --json number,title,labels --limit 20 2>/dev/null); GH_EXIT=$?
  # Quote: value contains parens, whitespace, em-dash (rule 2 of
  # references/command-output-format.md).
  echo "SINCE=\"(first release — using 20 most recent merged PRs)\""
fi
if [ $GH_EXIT -ne 0 ]; then
  echo "MERGED_PR_COUNT=0"
  echo "STATE=unavailable"
else
  MERGED_COUNT=$(echo "$MERGED_JSON" | jq 'length' 2>/dev/null)
  [ -z "$MERGED_COUNT" ] && MERGED_COUNT=0
  echo "MERGED_PR_COUNT=$MERGED_COUNT"
  if [ "$MERGED_COUNT" = "0" ]; then
    echo "STATE=empty"
  else
    echo "$MERGED_JSON" | jq -r '.[] | "MERGED_PR=number=\(.number) labels=\"\([.labels[].name] | join(","))\" title=\"\(.title)\""' 2>/dev/null
  fi
fi

echo ""
echo "### Commits Since Last Release"
# Capture so an empty range (right after a release) emits STATE=empty
# rather than a silent heading.
if [ "$LAST_TAG" != "none" ]; then
  COMMITS_RANGE=$(git log --oneline "$LAST_TAG"..HEAD 2>/dev/null)
else
  COMMITS_RANGE=$(git log --oneline -20 2>/dev/null)
fi
if [ -z "$COMMITS_RANGE" ]; then
  echo "STATE=empty"
else
  printf '%s\n' "$COMMITS_RANGE" | sed 's/^/COMMIT=/'
fi

true

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

  1. 4d ago First seen · 187 lines · 27 tokens per session scan A 58d1a3b633e2

Subscribe to this mod's changes

release is a command published in the GitHub repository synaptiai/synapti-marketplace (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 27 tokens to every session and 2,128 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-09-03.