A command that publishes matching releases for five related npm packages, which are JavaScript packages shared through npm. It checks the requested version change and starts the GitHub release process after confirmation.

Use it to release bug fixes, new features, or breaking changes across the package stack.

It prevents the packages from getting different version numbers and adds checks before a public release.

release — Command by mission69b

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/mission69b/t2000/release

Clone the repo

git clone --depth 1 https://github.com/mission69b/t2000

Made for: Claude Code.

Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 630 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.00019	$0.00630
Opus 5	$0.00010	$0.00315
Sonnet 5	$0.00004	$0.00126
Haiku 4.5	$0.00002	$0.00063

Measured 2d ago against content hash 5c6c57c970ad, 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 2d 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 · 64 lines

How it starts

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

Cut a release of the t2000 package stack. Bump type requested: $1 (default patch if empty).

Before anything, verify the bump is right

All 5 packages (sdk, cli, mcp, id, serve) move together to the same version — no drift.

Change	Bump
New tool, method, or command	`minor`
Bug fix, type fix, test fix	`patch`
Breaking change to code an external consumer could have written	`major`

Majors are rare — default down. Internal refactors, removals of unshipped or unused surface, and doc/catalog changes are minor at most. Never ship majors back-to-back; batch queued breaking removals into one. When in doubt, patch.

Look at git log since the last tag and state which bump the actual changes justify. If the requested bump disagrees with what the diff shows, say so and ask before proceeding.

Steps

Confirm the working tree is clean and you're on main (git status).
Confirm CI is green on the current HEAD.
Ask the user to confirm the version and bump type before triggering. This publishes to npm publicly and is not reversible.
Trigger the workflow:
```
gh workflow run release.yml --field bump=<patch|minor|major>
```
That runs .github/workflows/release.yml, which bumps all 5 package versions, commits 📦 build: vX.Y.Z, pushes the annotated tag, and dispatches publish.yml (CI → pnpm publish ×5 → GitHub Release → Discord #releases).
Watch it: gh run watch or gh run list --workflow=release.yml --limit 3.

Once npm publish completes, remind the user about the downstream bump:

cd /Users/funkii/dev/audric/apps/web-v3 && pnpm add @t2000/sdk@latest

Never do

Run npm --prefix packages/X version Y manually before pushing a tag.
Push a vX.Y.Z tag by hand.
Run pnpm publish locally.
Push multiple tags in one session to fix failures — fix the code, re-run the workflow.

Fallback

release.yml needs a RELEASE_TOKEN secret (a PAT with contents: write + branch-protection bypass). If the workflow fails on its push to main, that secret is missing — the manual fallback is documented in CLAUDE.md § Release process. Surface the failure to the user rather than silently switching to manual mode.

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

2d ago First seen · 64 lines · 19 tokens per session scan A 5c6c57c970ad

Subscribe to this mod's changes

release is a command published in the GitHub repository mission69b/t2000 (23 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 630 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-08-30.

Git and workflow Releases agent-commerce agent-economy agent-identity agent-marketplace agent-payments x402

release

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Before anything, verify the bump is right

Steps

Never do

Fallback

What this file has done since we first saw it

Other commands, from other repositories

help

mesh

review-renovate

release

ship

merge-and-status