commit

A command for committing code changes to version control. It also suggests splitting changes into separate commits when they cover different concerns.

In plain words
What is it for?
It is for creating commits and organising large changes into smaller, focused units.
Why use it?
It gives a clear way to save completed work while keeping unrelated changes separate.

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/mh4gf/claude-code/commit
Clone the repo
git clone --depth 1 https://github.com/MH4GF/claude-code
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 20 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 88% copy Near-identical to another mod 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.00000 $0.00020
Opus 5 $0.00000 $0.00010
Sonnet 5 $0.00000 $0.00004
Haiku 4.5 $0.00000 $0.00002

Measured yesterday against content hash badd2a1a6fce, 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 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.

Origin

This is a copy

88% identical to commit-and-pr — 2 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

user-scope-backup-2026-07-04/commands/commit.md · 3 lines

What it actually says

Let's commit the changes.

Split large changes: If changes touch multiple concerns, split them into separate 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. yesterday First seen · 3 lines · 0 tokens per session scan A badd2a1a6fce

Subscribe to this mod's changes

commit is a command published in the GitHub repository MH4GF/claude-code (2 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 20 tokens. A static security scan graded it A with 0 findings. It is 88% identical to commit-and-pr, differing in 2 lines, and is treated as a copy.