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/jeet129/praxis/releasegit clone --depth 1 https://github.com/jeet129/praxisWhat 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.00015 | $0.00417 |
| Opus 5 | $0.00008 | $0.00209 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00042 |
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 3d 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.
What it actually says
Run production-release.yaml workflow for the next release.
Ask me the release SHA (or use HEAD if just stated).
Assemble the production_go_live evidence pack per governance/governance.yaml:
ALWAYS REQUIRED (Wave 3 baseline):
- All pre-prod gates cleared (Code Review + Security Review + QA + staging verification).
- DR drill recent pass (per reliability-dr cadence).
- Capacity sizing verified (per capacity-resource-estimation).
- SLO observability live (per observability — SLOs, dashboards, alerts).
- Rollback plan documented (per deploy-release — triggers + procedure).
CONDITIONAL (Wave 4 additions; evaluate per charter flags + change characteristics): 6. Chaos engineering pass recent — assemble if flagged in scope by governance (resilience-critical change OR multi-AZ-region); otherwise record N/A with justification. 7. Performance test soak pass — if NFR-bearing change (latency / throughput / availability). 8. Compliance evidence complete — assemble if flagged in scope by governance (any regulated regime applies); otherwise record N/A with justification. 9. Threat model updated — if architecture or trust-boundary change. 10. Supply chain attestation verified — ALWAYS (SBOM + SLSA provenance).
If has_ml or has_agentic_ai: also assemble responsible_ai_review evidence pack (5 always + 5 conditional items).
Show me the assembled pack with each item shown explicitly. I review; approve or send back.
On approval: production_deploy executes; release record archived to .project/operational/releases/; release notes generated per technical-documentation.
Common rationalizations to ignore:
- "Small release; skip chaos." → chaos cadence is windowed (90 days); not per-release. Verify the latest pass is within window.
- "Rollback is just revert." → must be documented per
deploy-release. Trigger criteria + procedure + rehearsal date.
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.
- 3d ago First seen · 34 lines · 15 tokens per session scan A bf9a75182300
release is a command published in the GitHub repository jeet129/praxis (7 stars, last pushed 5d ago), licensed MIT. It adds 15 tokens to every session and 417 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-31.
Other commands, from other repositories
review-renovate
Review and merge renovate PRs with automerge configuration updates.
release
Perform a full release: generate release notes, bump version, commit, tag, and push.
release
Create a full stable release for the project. Optionally pass a title suffix (e.g., "Template Presets Fix") or extra notes.
SHIP_RELEASE
Ship the active release/X.Y.Z — build the installer, merge to main, tag, push, and publish the GitHub release. Run after /prerelease passes.
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.