Borrowing it
Nothing to install: this file belongs to rcconsult/ppxai. 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/rcconsult/ppxai/master/.claude/commands/release.mdgit clone --depth 1 https://github.com/rcconsult/ppxaiWrote 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/rcconsult/ppxai/release)<a href="https://agentmods.dev/commands/rcconsult/ppxai/release"><img src="https://agentmods.dev/badge/commands/rcconsult/ppxai/release/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/rcconsult/ppxai/release"><img src="https://agentmods.dev/badge/commands/rcconsult/ppxai/release.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01240 |
| Opus 5.5 | $0.00000 | $0.00496 |
| Sonnet 5.5 | $0.00000 | $0.00248 |
| Haiku 4.5 | $0.00000 | $0.00124 |
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 10d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Automated release for ppxai using scripts/release.py.
Arguments
$ARGUMENTS- Version number (e.g., v1.11.8)
Usage
Run the release script:
python scripts/release.py $ARGUMENTS
The script handles everything automatically:
- ✅ Checks git status (clean working directory)
- ✅ Checks branch (must be on master, use
--forceto release from feature branch) - ✅ Merges to master (if on feature branch with
--force) - ✅ Updates ALL version references:
- pyproject.toml (canonical Python SoT)
- ppxai/version.py (runtime SoT)
- vscode-extension/package.json (npm SoT)
- vscode-extension/package-lock.json (typed JSON edit)
- README.md (shields.io badge + tests-NNNN)
- docs/index.md (shields.io badge)
- ✅ Validates all version references with validate-release.py
- ✅ Creates release notes template if missing
- ✅ Runs TypeScript lint on VSCode extension
- ✅ Runs tests
- ✅ Creates commit and tag
- ✅ Pushes to GitHub (always pushes master branch)
- ✅ Waits for CI to complete
- ✅ Publishes release notes to GitHub release
- ✅ Builds Intel Mac assets (auto-detects platform)
- ✅ Verifies all assets are present
Script Options
# Dry run - show what would be done without making changes
python scripts/release.py v1.11.8 --dry-run
# Skip tests (use with caution)
python scripts/release.py v1.11.8 --skip-tests
# Don't wait for CI (useful if you'll check manually)
python scripts/release.py v1.11.8 --skip-ci-wait
# Force release from feature branch (merges to master first)
python scripts/release.py v1.11.8 --force
# REDO: Delete broken release and rebuild from scratch
python scripts/release.py v1.11.8 --redo
Redo a Broken Release
If something went wrong with a release, use --redo to:
- Delete the GitHub release
- Delete the remote and local tags
- Reset master if the last commit was the release commit
- Then proceed with a fresh release
# Redo a broken release
python scripts/release.py v1.11.7 --redo
# Redo with force (if you have local changes to include)
python scripts/release.py v1.11.7 --redo --force
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.
- 10d ago Changed · -8 lines 6c71b20cf7ec
- 1mo ago First seen · 158 lines · 0 tokens per session scan A 8507dbbd4a32
release is a command published in the GitHub repository rcconsult/ppxai (6 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,240 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-31.
Other commands, from other repositories
land
Resolve and squash merge one named, currently authorized pull request.
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.
quality
A command for temporarily clearing a release quality gate or one named check, while recording the reason and expiry time. A quality gate is a required check that normally blocks completion or release.
create-pr
Push the current branch and open a pull request into main with a structured description derived from the branch's commits and the open issues it resolves.
release-manager
Automated release coordination and deployment with ruv-swarm orchestration for seamless version management, testing, and deployment across multiple packages.
doc-changelog
Generation and maintenance of the project changelog.