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 commands/rcconsult/ppxai/releasegit clone --depth 1 https://github.com/rcconsult/ppxaiWhat 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.00000 | $0.01251 |
| Opus 5 | $0.00000 | $0.00626 |
| Sonnet 5 | $0.00000 | $0.00250 |
| Haiku 4.5 | $0.00000 | $0.00125 |
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.
How it starts
The opening of the file, as written. The whole thing — 158 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
- ppxai/init.py
- vscode-extension/package.json
- vscode-extension/package-lock.json
- ppxai/common/event_handler.py
- README.md (vsix references)
- vscode-extension/README.md (vsix references)
- CLAUDE.md (current version + version alignment)
- ROADMAP.md (current release)
- ✅ 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
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 · 158 lines · 0 tokens per session scan A 8507dbbd4a32
release is a command published in the GitHub repository rcconsult/ppxai (5 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,251 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.