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/ohswedd/praxis/shipgit clone --depth 1 https://github.com/Ohswedd/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.00019 | $0.00431 |
| Opus 5 | $0.00010 | $0.00216 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
ship 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.
What it actually says
Use the git-delivery skill. Read ${ARGUMENTS} to pick the mode.
Default: deliver the current change. Precondition: the praxis audit is green
and the tree holds only the intended change. Write a Conventional Commit, branch
if on the default branch, push, and open a PR with a structured body. Check the
live merge policy with python3 "${CLAUDE_PLUGIN_ROOT}/scripts/config.py" status
and follow it: merge only when auto-merge is ON and the audit and any required
checks are green, otherwise stop at the PR and hand it to the user. Finish by
reporting the PR URL and the merge state.
release [version]: cut a release.
- Review what is pending:
changelog.py show. - Determine the next version, unless one was given, from the commits since the
last tag and the
[Unreleased]entries, applying SemVer per Conventional Commits: breaking to MAJOR,featto MINOR,fix/perfto PATCH. State your reasoning. - Finalize the changelog into a dated section:
changelog.py release <version>. - Bump every version file the project uses (package.json, pyproject.toml, plugin and marketplace manifests) so they agree.
- Prepare, without pushing until the user confirms, the commit
chore(release): v<version>and the tagv<version>. Show the diff first.
Match the project's existing release process where it has one. Scripts live under
${CLAUDE_PLUGIN_ROOT}/scripts/.
Never add an AI co-author trailer or a "generated with" credit to a commit, tag, PR body, or release note. The PreToolUse guard blocks the command outright.
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 · 34 lines · 19 tokens per session scan A 57ea50565c79
ship is a command published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 431 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
pr-submit
Create git commit and submit current branch with Graphite (squashes commits and rebases stack).
ship
Commit all changes, push branch, create/update PR, and run local validation.
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
commit-push-pr
Commit, push, and open a PR.
ship
Ship: review gate, tests, version bump, changelog, conventional commit, docs update, PR. Complete pipeline from done to merged.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…