Borrowing it
Nothing to install: this file belongs to Parslee-ai/neo. 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/Parslee-ai/neo/main/.claude/commands/prepare-release.mdgit clone --depth 1 https://github.com/Parslee-ai/neoWrote 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/parslee-ai/neo/prepare-release)<a href="https://agentmods.dev/commands/parslee-ai/neo/prepare-release"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/prepare-release.svg" alt="Measured on agentmods" 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.00017 | $0.01002 |
| Opus 5 | $0.00009 | $0.00501 |
| Sonnet 5 | $0.00003 | $0.00200 |
| Haiku 4.5 | $0.00002 | $0.00100 |
Grade A, and why
prepare-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 8d 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare Release
Updates version numbers, CHANGELOG.md, and builds distributions for a new release.
Usage
/prepare-release 0.7.7
What This Does
- Validates the new version is higher than current and follows semver format
- Reviews commits since last release tag
- Updates CHANGELOG.md with new version section and categorized changes
- Updates the version in
pyproject.toml— the single source of truth — and runsmake sync-versionto propagate it to the three derived files - Builds wheel and sdist distributions
- Reports what was done and next steps
Workflow
Step 1: Validate
- Read current version from
pyproject.toml - Verify new version is higher and matches format
X.Y.Z - Check that last git tag exists (e.g.,
v0.7.6)
Step 2: Analyze Commits
Run git log v{last_version}..HEAD --oneline and categorize by type:
- Fixed: Commits with "fix:" prefix or fixing bugs
- Added: Commits with "feat:" prefix or new features
- Changed: Commits with "refactor:" or "perf:" or improvements
- Documentation: Commits with "docs:" prefix
Step 3: Update CHANGELOG
Add new section at top of CHANGELOG.md:
## [{new_version}] - {today's date}
### Fixed
- List of bug fixes from commits
### Added
- List of new features from commits
### Changed
- List of improvements from commits
### Documentation
- List of doc updates from commits
Step 4: Update Versions
Edit ONE file, then propagate. pyproject.toml is the source of truth:
# 1. Change `version = "X.Y.Z"` in pyproject.toml (the only hand edit)
make sync-version # propagates to the three derived files
python tools/sync_version.py --check # confirms all four in sync
make sync-version rewrites src/neo/__init__.py, .claude-plugin/plugin.json
and plugins/neo/.codex-plugin/plugin.json. Never hand-edit those three —
they are derived, and tests/test_host_adapter_parity.py fails if they drift
from pyproject.toml.
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.
- 8d ago First seen · 125 lines · 17 tokens per session scan A 4409f5d813b8
prepare-release is a command published in the GitHub repository Parslee-ai/neo (16 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 1,002 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.
Other commands, from other repositories
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
ship
Ship is the operational release-prep flow for a connected project repo.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.
release
Standalone SDK release command for the BUILD repo. Not a workspace phase — runs independently after any number of implement/redteam cycles. Handles PyPI publishing, documentation deployment, and CI management for the kailash Python SDK and its framework packages.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and issue references.