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 skills/ohswedd/praxis/git-deliverynpx skills add Ohswedd/praxis --skill git-deliverygit clone --depth 1 https://github.com/Ohswedd/praxisWrote 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/ohswedd/praxis/git-delivery)<a href="https://agentmods.dev/skills/ohswedd/praxis/git-delivery"><img src="https://agentmods.dev/badge/skills/ohswedd/praxis/git-delivery.svg" alt="Measured on agentmods" 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 | $0.00137 | $0.02364 |
| Opus 5 | $0.00068 | $0.01182 |
| Sonnet 5 | $0.00027 | $0.00473 |
| Haiku 4.5 | $0.00014 | $0.00236 |
Grade A, and why
git-delivery 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.
How it starts
The opening of the file, as written. The whole thing — 172 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Delivery
The last mile: turn an audited change into a clean commit and a reviewable pull request. Delivery is explicit and only when needed: praxis does not commit or push on every edit. Run this once a change is complete and its audit is green.
Preconditions. The praxis audit is green, tests pass, and the working tree holds only the intended change. If secrets are present or the audit is red, stop and fix, never deliver an unreviewed or unsafe change.
1. Commit: Conventional Commits
Match the repo's existing history first; where it already uses Conventional Commits, follow it:
<type>(<scope>): <subject>
<body: what changed and why, not how>
<footer: BREAKING CHANGE: ... | Refs #123>
- type:
feat,fix,docs,refactor,perf,test,build,ci,chore. - subject: imperative mood, no trailing period, ≤ 72 characters.
- body: motivation and effect; wrap at ~72 columns; omit for trivial changes.
- BREAKING CHANGE footer (or
type!:) for any incompatible change. - One logical change per commit: stage intentionally; do not bundle unrelated work
or blindly
git add -Aacross a mixed tree. - No AI/tool attribution, enforced. No
Co-Authored-Bytrailer for Claude or any AI, no "generated with" credit, no robot emoji, in the message, the body, or the footer. The history is the project's own. Describing the platform ("praxis is a Claude Code plugin") is fine; crediting authorship is not. The PreToolUse guard refuses anygit commit,git tag,gh pr create,gh release createorgh issuecommand that carries one, so this is not a matter of remembering: the command will simply be blocked, and once a credit is committed it is in the history for good.
Never commit secrets, credentials, or local state (respect .gitignore). The
PreToolUse guard blocks force-pushes and destructive resets; delivery works within
it, and it also refuses to stage CLAUDE.local.md, .claude/.praxis/ or
.claude/settings.local.json, which describe your machine rather than the
project and belong in no repository's history.
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 · 172 lines · 137 tokens per session scan A 75661555b29f
git-delivery is a skill published in the GitHub repository Ohswedd/praxis (1 stars, last pushed 1mo ago), licensed MIT. It adds 137 tokens to every session and 2,364 once invoked, about $0.0007 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
handoff
Ship completed work: verify locally, commit related changes, push, create or update the PR, watch CI/reviews, and fix until merge-ready or escalated. Use for "ship it", "create PR", "handoff", or finished code needing delivery.
arn-code-ship
This skill should be used when the user says "ship it", "arness code ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", or wants to commit, push, and optionally open a pull request. Guides…
arn-shipping
This skill should be used when the user says "shipping", "arness shipping", "ship it", "ship", "create PR", "open pull request", "push and PR", "commit and push", "wrap up", "ship the feature", "ship the fix", "ready to ship", "push changes", "finalize", "finish up", "done", "arn-shipping", or wants to commit, push…
smart-git-commit
Use this skill for ANY git operation — commits, pushes, PRs, releases, or version tagging. Triggers on: "commit", "push", "save my changes", "create a PR", "open a pull request", "ship this", "make a release", "tag this version", "checkpoint my work", or any request to record or publish code changes. Produces…
scribe
Route mechanical git prose — commit messages, PR titles/bodies, release notes, changelog entries — to the cheapest healthy model (free local ollama first) instead of burning main-session tokens. Use whenever the user asks to commit, open a PR, cut a release, or write a changelog and the prose can be drafted from the…
git-flow
Use when creating a branch, using worktrees for parallel work, committing, or wrapping up. Covers branch naming, conventional commits, short-lived branches, worktree isolation, and final merge/cleanup.