commit

A command that reviews repository changes and prepares them as logical Git commits. Conventional commits use a standard format to describe changes, such as fixes or new features.

In plain words
What is it for?
Use it before sharing work or opening a review when changes need to be grouped and committed cleanly.
Why use it?
It turns a mixed or unclear set of edits into organized commits with descriptive messages.

Command

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.

agentmods
npx agentmods add commands/alleneubank/claude-code/commit
Clone the repo
git clone --depth 1 https://github.com/alleneubank/claude-code
Per session 4 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 112 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00004 $0.00112
Opus 5 $0.00002 $0.00056
Sonnet 5 $0.00001 $0.00022
Haiku 4.5 $0.00000 $0.00011

Measured 2d ago against content hash 3afec8da5bed, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

commands/commit.md · 16 lines

What it actually says

Context

  • Current git status: !git status
  • Current git diff (staged and unstaged changes): !git diff HEAD
  • Current branch: !git branch --show-current
  • Recent commits: !git log --oneline -10

Your task

Review the changes in the repo and prepare logical, organized, clean and descriptive git commits using conventional commits.

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. 2d ago First seen · 16 lines · 4 tokens per session scan A 3afec8da5bed

Subscribe to this mod's changes

commit is a command published in the GitHub repository alleneubank/claude-code (52 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 4 tokens to every session and 112 once invoked, about $0.0000 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-30.