agentmods.dev

release

release is a command for Claude Code from ljucask/pureinn-product-development. It costs 40 tokens per session (515 once invoked), scanned A, original, MIT.

A guided command for publishing a new version of the Pureinn framework. It reviews the changes, proposes a version increase and release note, then publishes only after the user confirms.

In plain words
What is it for?
Use it to inspect changes since the last release, choose a patch, minor, or major version according to the repository's rules, and publish the confirmed release to GitHub.
Why use it?
It reduces the chance of releasing the wrong changes, version, or message by making the release decision explicit before committing and tagging it.

Command for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions CLAUDE.md.

Not installable on its own: it runs a file from its repository that does not travel with it. Clone the repository, or install whatever ships that file. The line is ./scripts/release.sh <bump> "<message>" --yes.

Part of the pureinn-product-development plugin — 51 skills, 1 command shipped together

not rated 2 26d ago A scan 40 tokens original MIT
View the source file ljucask/pureinn-product-development
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 ljucask/pureinn-product-development
Claude Code
/plugin install pureinn-product-development

Made for: Claude Code.

Or install pureinn-product-development, the plugin that ships this one along with the rest of its 51 skills, 1 command.

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/ljucask/pureinn-product-development/release.svg)](https://agentmods.dev/commands/ljucask/pureinn-product-development/release)
Your own site
<a href="https://agentmods.dev/commands/ljucask/pureinn-product-development/release"><img src="https://agentmods.dev/badge/commands/ljucask/pureinn-product-development/release.svg" alt="Measured on agentmods" height="20"></a>
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 515 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.1 $0.00040 $0.00515
Opus 5 $0.00020 $0.00258
Sonnet 5 $0.00008 $0.00103
Haiku 4.5 $0.00004 $0.00052

Measured 5d ago against content hash ffad229b3a5b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, 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 5d 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 · 28 lines

What it actually says

The user wants to publish a release of the framework (this repo). Run this flow. Triggers: /release, or natural phrases like "urob release", "aktualizuj git", "vydaj novú verziu".

  1. Inspect what changed since the last release: run git status and git --no-pager diff (and git log <lastTag>..HEAD --oneline if useful). Understand what actually changed - do not guess.

  2. Decide the version bump per the repo's rules in CLAUDE.md:

    • patch: bug fix, text correction, clarification
    • minor: new skill, significant skill update, new integration
    • major: renamed/removed skill, breaking workflow/structure change Note: the release history is deliberately kept to major+minor only (patches are treated as noise). Prefer minor for real content changes; use patch only for genuine fixes.

  3. Draft a one-line release message describing the change, in the style of existing releases (see git tag / CHANGELOG.md).

  4. Confirm with the user before publishing. Show: the bump type, the resulting version number, and the message. Ask if it is correct or should be adjusted. Do NOT publish until the user confirms. If the user wants changes, update and re-confirm.

  5. Publish once confirmed: run

    ./scripts/release.sh <bump> "<message>" --yes

    The script bumps the version, syncs skill/command counts across plugin.json/marketplace.json/README/CLAUDE.md, updates the CHANGELOG, then commits, pushes, tags, and creates the GitHub Release. --yes is correct here because you already confirmed with the user in step 4.

  6. Report the result: the new version, and that the website (pureinn-web) will rebuild automatically via the deploy-web GitHub Action pinging the Vercel deploy hook. No further action is needed for the web.

If there are no uncommitted changes and no unreleased commits since the last tag, tell the user there is nothing to release rather than cutting an empty version.

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. 5d ago First seen · 28 lines · 40 tokens per session scan A ffad229b3a5b

Subscribe to this mod's changes

release is a command published in the GitHub repository ljucask/pureinn-product-development (2 stars, last pushed 26d ago), licensed MIT. It adds 40 tokens to every session and 515 once invoked, about $0.0002 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 workflowReleasesai-agentsai-nativeclaude-codeclaude-pluginfddfeature-driven-development
Related

Other commands, from other repositories

ship

交付出包 · 串行跑 /package → /report，并打包所有交付产物。.

dhslegen/digital-delivery-team · 23 tokens

release-sync

Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.

yonatangross/orchestkit · 62 tokens

operations-agent

Deployment phase agent - build, deploy, verify, and monitor releases.

fabriqaai/specs.md · 13 tokens

ship

Open a pull request for the current branch, drive it green, and merge it.

Cavalry-Collective/visual-stack · 16 tokens

moodle-bump-version

You will bump the Moodle plugin version and wire the upgrade step.

SaadRahman01/claude-moodle-dev · 0 tokens

release

Cut a Major.Minor release from the Increment.

nunoamorim99/agile-ledger · 9 tokens