A release command for publishing a new version of the LAP project to PyPI and npm, two package registries used to distribute Python and JavaScript packages.

Use it to validate a semantic version, run the test suite, update project and TypeScript package versions, update the changelog, and publish the packages.

It coordinates version checks, tests, version updates, changelog changes, and possible documentation updates in one release process. It stops if the tests fail.

release — Command by Lap-Platform

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/lap-platform/lap/release

Clone the repo

git clone --depth 1 https://github.com/Lap-Platform/LAP

Made for: Claude Code.

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 578 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00578
Opus 5	$0.00000	$0.00289
Sonnet 5	$0.00000	$0.00116
Haiku 4.5	$0.00000	$0.00058

Measured yesterday against content hash ca3a040f8f0a, 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 yesterday.

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 · 42 lines

How it starts

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

Release a new version of LAP

Bump the version and publish to PyPI + npm.

Arguments

$ARGUMENTS: The new version number (e.g. "0.5.0"). If empty, ask the user.

Steps

Validate version: Ensure the version argument is a valid semver string (X.Y.Z). If not provided or invalid, ask the user for the version number.
Run tests first: Run PYTHONUTF8=1 python -m pytest tests/ -q --timeout=30 from the project root. If any tests fail, STOP and report the failures. Do not proceed with a broken build.
Bump version in all files:
- lap/__init__.py -- update __version__
- pyproject.toml -- update version
- sdks/typescript/package.json -- update version
Update CHANGELOG.md: Add a new ## [X.Y.Z] - YYYY-MM-DD section at the top (below the header). Ask the user for a summary of changes, or generate one from recent git log if the user says to auto-generate.
Update README.md: Review the changelog for this release. If it includes new features, new commands, new IDE support, or changed behavior that users need to know about, update README.md accordingly (Quick Start, Use as an Agent Skill, Ecosystem table, badges, etc.). If the release is only bug fixes or internal changes, skip this step.
Commit: Stage all changed files and commit with message: chore: bump to vX.Y.Z with changelog
Push: Push to origin/main.
Create GitHub Release: Run gh release create vX.Y.Z --title "vX.Y.Z" --notes-file CHANGELOG_SECTION where CHANGELOG_SECTION contains only the new version's changelog section.
Monitor publish workflows: After the release is created, poll the two workflow runs:
- Publish to PyPI
- Publish to npm
Use gh run list --limit 4 to find the run IDs, then use gh run watch <run-id> to monitor each. Report the final status of each workflow to the user (success/failure). If a workflow fails, show the failure logs using gh run view <run-id> --log-failed.

Important

Never skip tests before releasing
All three version files must be in sync
The GitHub release triggers the publish workflows via on: release: types: [published]
Do not publish manually -- always use the GitHub Actions workflows

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

yesterday First seen · 42 lines · 0 tokens per session scan A ca3a040f8f0a

Subscribe to this mod's changes

release is a command published in the GitHub repository Lap-Platform/LAP (346 stars, last pushed 14d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 578 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.

Backend and APIs Git and workflow Testing ai-agents api cli developer-tools graphql openapi

add_and_commit

add and commit with descriptive message.

specmatic/specmatic-mcp-server · 0 tokens

smoke-test

npm run test:smoke.

specmatic/specmatic-mcp-server · 0 tokens

checkpoint

Create a checkpoint by staging the changes you have made using git. usage: git [-v | --version] [-h | --help] [-C ] [-c = ] [--exec-path[= ]] [--html-path] [--man-path] [--info-path] [-p | --paginate | -P | --no-pager] [--no-replace-objects] [--bare] [--git-dir= ] [--work-tree= ] [--namespace= ] [--super-prefix= ]…

TracecatHQ/tracecat · 0 tokens

release