Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jeet129/praxisnpx agentmods add skills/jeet129/praxis/praxis-releaseWrote 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/jeet129/praxis/praxis-release)<a href="https://agentmods.dev/skills/jeet129/praxis/praxis-release"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-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/skills/jeet129/praxis/praxis-release"><img src="https://agentmods.dev/badge/skills/jeet129/praxis/praxis-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.00034 | $0.00287 |
| Opus 5 | $0.00017 | $0.00143 |
| Sonnet 5 | $0.00007 | $0.00057 |
| Haiku 4.5 | $0.00003 | $0.00029 |
Grade A, and why
praxis-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.
What it actually says
capability: command
domain: codex-plugin
state: active
dependencies: [deploy-release, cicd-pipeline, observability, reliability-dr, capacity-resource-estimation, supply-chain-security]
triggers: [praxis release, production release, go live, deploy production]
outputs: [production_go_live_pack, deployment_record, verification_report, release_record]
consumers: [praxis-steward]
references: [../../workflows/production-release.yaml, ../../governance/governance.yaml]
Praxis Release
Run the production release workflow.
- Read
workflows/production-release.yamlandgovernance/governance.yaml. - Ask for the release SHA or use the stated candidate commit.
- Assemble the
production_go_liveevidence pack from governance. - Evaluate conditional evidence rules and mark each item
required,not_applicable, orblocked. - Stop for user approval before production deployment.
- On approval, execute deployment, post-deploy verification, rollback if needed, and release record creation.
Do not use a reduced evidence checklist when governance requires more.
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 First seen · 31 lines · 34 tokens per session scan A 4fe68f5b04fe
praxis-release is a skill published in the GitHub repository jeet129/praxis (7 stars, last pushed 5d ago), licensed MIT. It adds 34 tokens to every session and 287 once invoked, about $0.0002 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 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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.
updater_guide
Guidance for checking for and installing Row-Bot updates.