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/elixpo/claudeops.elixpo/commit-push-prgit clone --depth 1 https://github.com/elixpo/claudeOps.elixpoWrote 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/commands/elixpo/claudeops.elixpo/commit-push-pr)<a href="https://agentmods.dev/commands/elixpo/claudeops.elixpo/commit-push-pr"><img src="https://agentmods.dev/badge/commands/elixpo/claudeops.elixpo/commit-push-pr.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.00000 | $0.00770 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
commit-push-pr 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 4d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commit, push, and open a PR. Branch rules prevent accidents on main or duplicate PRs.
Step 1 — Detect branch state
git branch --show-current
If on main
- NEVER commit to main. Create a new branch first.
- For agent runs:
BRANCH="elixpo/issue-$ISSUE_N-$(openssl rand -hex 2)" - For human work:
feat/<slug>orfix/<slug> git checkout -b "$BRANCH", continue to Step 2.
If on a feature branch
Check whether this branch already has an open PR:
gh pr list --head "$(git branch --show-current)" --state open --json number,url --jq '.[0]'
- Open PR exists → push to this branch (Step 2). Do NOT open another PR.
- No open PR → check for a merged one:
gh pr list --head "$(git branch --show-current)" --state merged --json number --jq '.[0].number'- Merged → branch is stale. Cut a fresh branch from
main:
Re-apply the change there.git checkout main && git pull && git checkout -b elixpo/issue-$ISSUE_N-$(openssl rand -hex 2) - Never had a PR → push and open a new one (Step 3).
- Merged → branch is stale. Cut a fresh branch from
Step 2 — Biome, commit, push
./biome.sh— apply fixes../biome.sh ci— must exit 0. If it fails, read the output, fix the errors by hand, re-run.git status+git diff --stat— sanity-check what's staged.git addspecific files — avoid.env*,.wrangler/, anything undertsconfig.tsbuildinfo.- Commit with conventional format:
feat: <concrete summary> (#<issue-n>) fix: <concrete summary> (#<issue-n>) git push -u origin HEAD(first push) orgit push(subsequent).
Step 3 — Open PR (only if no open PR already)
gh pr create --base main --head "$(git branch --show-current)" \
--title "[ELIXPO] <short>" \
--body "$(cat <<'EOF'
## What this does
<2-4 sentences, user-visible outcome>
## Why
<1-2 sentences referencing the trigger or issue>
## Changes
- `<file>`: <what changed and why>
- <3-6 bullets; concrete, not vague>
## Verification
- `./biome.sh ci` clean
- <tests pass / dev-server verified / not verified — pick one>
---
Fixes #<issue-n>
EOF
)"
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.
- 4d ago First seen · 85 lines · 0 tokens per session scan A ca58ce5e049f
commit-push-pr is a command published in the GitHub repository elixpo/claudeOps.elixpo (2 stars, last pushed 24d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 770 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
commit
Auto-stage, review, and commit all changes with a conventional commit message.
ship
Commit all changes and push to remote in one operation (combines /commit and /push).
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
autocommit
Toggle auto git commits on/off for this project. Run without args to see status, or with "on"/"off" to set.
commit-message
Generate a conventional commit message from staged changes.
iterate
Iteration delivery — delivery check + archive + commit & tag + bump version.