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.
npx agentmods add skills/parslee-ai/neo/source-command-ship-releasenpx skills add Parslee-ai/neo --skill source-command-ship-releasegit 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/skills/parslee-ai/neo/source-command-ship-release)<a href="https://agentmods.dev/skills/parslee-ai/neo/source-command-ship-release"><img src="https://agentmods.dev/badge/skills/parslee-ai/neo/source-command-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.00016 | $0.00844 |
| Opus 5 | $0.00008 | $0.00422 |
| Sonnet 5 | $0.00003 | $0.00169 |
| Haiku 4.5 | $0.00002 | $0.00084 |
Grade A, and why
source-command-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 6d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
source-command-ship-release
Use this skill when the user asks to run the migrated source command ship-release.
Command Template
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 version in pyproject.toml, src/neo/init.py, .claude-plugin/plugin.json, plugins/neo/.codex-plugin/plugin.json
- Refreshes the local editable install metadata and verifies
importlib.metadata.version("neo-reasoner") == "{version}" - 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}"
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
- Verify local install metadata reports the release version:
python -c "import importlib.metadata as m; print(m.version('neo-reasoner'))" - Merge the PR
Then run: /ship-release {version} --continue
Phase 5: Create Tag (after PR merge)
git checkout main
git pull origin main
git tag v{version}
git push origin v{version}
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.
- 6d ago First seen · 127 lines · 16 tokens per session scan A 1f822808ee41
source-command-ship-release is a skill published in the GitHub repository Parslee-ai/neo (16 stars, last pushed today), licensed Apache-2.0. It adds 16 tokens to every session and 844 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog
Create changelog files for important commits in a PR.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
refresh-arm-sdk-release
WORKFLOW SKILL — Prepares Azure.ResourceManager SDK refresh pull requests in azure-sdk-for-net. WHEN: "prepare sdk refresh", "refresh Azure.ResourceManager package", "update ARM SDK from autorest tag", "refresh changelog dependencies". INVOKES: git and GitHub pull request tools for branch, commit, push, and PR…