apex-git-commit

apex-git-commit is a command for Claude Code, GitHub Copilot from jonathan-vella/apex-accelerator. It costs 52 tokens per session (1,765 once invoked), scanned A, original, MIT.

A Git command that stages selected changes, creates a Conventional Commit message, pushes the current branch, and asks whether to open or update a GitHub pull request. Git tracks code changes, while a pull request is a request for review before merging.

In plain words
What is it for?
It is for committing work, pushing a feature branch, and opening or updating a pull request from the command line.
Why use it?
It removes repetitive release-to-review steps while keeping specified files out of the commit and avoiding direct commits to the main branch.

Command for Claude CodeGitHub Copilot

Written for Claude Code and GitHub Copilot: argument-hint in frontmatter, but also a Copilot chat mode or prompt. Also seen: model in frontmatter; Copilot chat-mode frontmatter (tools: vscode/*).

Good fit It is for committing work, pushing a feature branch, and opening or updating a pull request from the command line.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jonathan-vella/apex-accelerator/apex-git-commit
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jonathan-vella/apex-accelerator

Made for: Claude Code, GitHub Copilot.

Wrote 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.

agentmods badge for apex-git-commit

README.md
[![agentmods](https://agentmods.dev/badge/commands/jonathan-vella/apex-accelerator/apex-git-commit.svg)](https://agentmods.dev/commands/jonathan-vella/apex-accelerator/apex-git-commit)
Your own site
<a href="https://agentmods.dev/commands/jonathan-vella/apex-accelerator/apex-git-commit"><img src="https://agentmods.dev/badge/commands/jonathan-vella/apex-accelerator/apex-git-commit.svg" alt="Measured on agentmods" height="20"></a>
Per session 52 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,765 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00052 $0.01765
Opus 5 $0.00026 $0.00882
Sonnet 5 $0.00010 $0.00353
Haiku 4.5 $0.00005 $0.00177

Measured yesterday against content hash f59f4ab7a373, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

apex-git-commit 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 yesterday.

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.

.github/prompts/apex-git-commit.prompt.md · 207 lines

How it starts

The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Commit, Push & PR (CLI-only)

Stage all changes except anything under agent-output/, infra/, or .github/skills/sensei/ (the sensei exclusion is lifted only when the current branch is feat/skills-sensei), auto-generate a conventional commit, push to the current branch, then ask whether to open a new PR or update an existing one. Uses git and gh only — no MCP tools.

Scope

  • Workspace must be a git repository with origin configured.
  • gh CLI must be authenticated (GH_TOKEN is set in the devcontainer).
  • Excluded paths (always): agent-output/, infra/.
  • Excluded path (conditional): .github/skills/sensei/ — included only when git branch --show-current returns feat/skills-sensei.
  • Never commit to main. Never force-push.

Inputs

Variable Source Default
subject argument-hint or generated from diff auto
branch git branch --show-current current branch
sensei derived: branch == feat/skills-sensei exclude sensei
pr_mode user choice (new / update / skip) ask
pr_base user choice main

Workflow

Step 0 — Compute the exclusion pathspec

Resolve the active branch and build the pathspec used by every subsequent git command:

BRANCH="$(git branch --show-current)"
if [[ "$BRANCH" == "feat/skills-sensei" ]]; then
  EXCLUDES=(':!agent-output' ':!infra')
else
  EXCLUDES=(':!agent-output' ':!infra' ':!.github/skills/sensei')
fi

Every git add/git status/git diff command below uses -- . "${EXCLUDES[@]}" to apply the exclusion list consistently. If the user is on feat/skills-sensei the sensei skill files are eligible for staging; on every other branch they are skipped.

Step 1 — Inspect

Run these in parallel and show the output:

echo "$BRANCH"
git status --short -- . "${EXCLUDES[@]}"
git diff --stat HEAD -- . "${EXCLUDES[@]}"

Read the full file on GitHub · 207 lines

Changes

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.

  1. yesterday First seen · 207 lines · 52 tokens per session scan A f59f4ab7a373

Subscribe to this mod's changes

apex-git-commit is a command published in the GitHub repository jonathan-vella/apex-accelerator (50 stars, last pushed yesterday), licensed MIT. It adds 52 tokens to every session and 1,765 once invoked, about $0.0003 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-09-07.