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/ship-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/ship-release)<a href="https://agentmods.dev/commands/parslee-ai/neo/ship-release"><img src="https://agentmods.dev/badge/commands/parslee-ai/neo/ship-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.00013 | $0.01747 |
| Opus 5 | $0.00006 | $0.00873 |
| Sonnet 5 | $0.00003 | $0.00349 |
| Haiku 4.5 | $0.00001 | $0.00175 |
Grade A, and why
ship-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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ship Release
Orchestrates the full release workflow: version prep, PR creation, tagging, and PyPI publication.
Usage
/ship-release 0.7.7
What This Does
Runs the complete release workflow for projects with protected main branches:
- Invokes
/prepare-releaseto update versions and changelog - Creates release branch (
release/v{version}) - Commits the changes
- Pushes branch and creates PR
- PAUSES for human PR review and merge
- After merge, creates git tag
- Creates GitHub Release (triggers PyPI publish via Actions)
- Monitors PyPI publication
Workflow
Phase 1: Prepare Release
Run /prepare-release {version} which:
- Updates CHANGELOG.md
- Updates the version in
pyproject.toml(the only hand edit) and runsmake sync-versionto propagate it tosrc/neo/__init__.pyand both plugin manifests - Builds distributions
Phase 2: Create Release Branch
git checkout -b release/v{version}
If branch already exists, check it out instead.
Phase 3: Commit Changes
git add CHANGELOG.md pyproject.toml src/neo/__init__.py \
.claude-plugin/plugin.json plugins/neo/.codex-plugin/plugin.json
git commit -m "chore: bump version to {version}"
Four version files, not three — the Codex plugin manifest is the one that gets
forgotten. python tools/sync_version.py --check should report all four in sync
before committing.
Phase 4: Push and Create PR
git push origin release/v{version}
gh pr create --title "Release v{version}" --body "<changelog summary>"
CHECKPOINT: Command stops here. Report PR URL and next steps.
User must:
- Review the PR
- Verify changelog and version updates
- Merge the PR
Then run: /ship-release {version} --continue
Phase 5: Create Tag (after PR merge)
Verify the release PR actually merged before tagging. This phase only pulls
main and tags it, so running --continue early tags a tree with no version
bump — and Phase 6 then publishes anyway, leaving PyPI carrying {version} while
the tag points at a commit that still says the previous one. Nothing downstream
catches that.
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 · 196 lines · 13 tokens per session scan A 970ef66b12e9
ship-release is a command published in the GitHub repository Parslee-ai/neo (16 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 1,747 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.