git-commit

A command for staging relevant Git changes and creating a commit, which is a saved checkpoint in a code repository.

In plain words
What is it for?
It is for preparing and committing completed code changes.
Why use it?
It helps ensure the changes are included and the commit message follows the project’s conventions.

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/cfircoo/claude-code-toolkit/git-commit
Clone the repo
git clone --depth 1 https://github.com/cfircoo/claude-code-toolkit
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 161 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.00008 $0.00161
Opus 5 $0.00004 $0.00081
Sonnet 5 $0.00002 $0.00032
Haiku 4.5 $0.00001 $0.00016

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

Security

Grade A, and why

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.

commands/git-commit.md · 30 lines

What it actually says

Invoke the git skill for: commit $ARGUMENTS

<success_criteria>

  • All relevant changes staged
  • Commit message follows repository conventions
  • Commit created successfully </success_criteria>
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 · 30 lines · 8 tokens per session scan A f25a75fbc1dc

Subscribe to this mod's changes

git-commit is a command published in the GitHub repository cfircoo/claude-code-toolkit (17 stars, last pushed 5mo ago), licensed MIT. It adds 8 tokens to every session and 161 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.