commit

A Git command that reviews your project changes and creates commits using the project's configured message style. Git commits are saved checkpoints in a code project's history.

In plain words
What is it for?
Use it to review staged, modified, and new files, understand what changed, and create one or more new commits without rewriting existing commits.
Why use it?
It reduces the manual work of inspecting changes, choosing files, and writing consistently formatted commit messages. It also applies rules intended to avoid unsafe staging and sensitive files.

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/bityoungjae/marketplace/commit
Clone the repo
git clone --depth 1 https://github.com/BitYoungjae/marketplace
Per session 10 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,426 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.00010 $0.01426
Opus 5 $0.00005 $0.00713
Sonnet 5 $0.00002 $0.00285
Haiku 4.5 $0.00001 $0.00143

Measured 2d ago against content hash f3ef4edd0555, 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.

plugins/gitkkal/commands/commit.md · 181 lines

How it starts

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

gitkkal commit

Analyzes changes and creates commits following the configured style.

Critical Rules

  • NEVER include Co-Authored-By lines in commit messages
  • NEVER use git commit --amend — always create NEW commits
  • NEVER use git add -A or git add . — stage files individually
  • NEVER commit sensitive files (.env, credentials, API keys)
  • ALWAYS use HEREDOC for commit messages to ensure proper formatting

Workflow

1. Load Configuration

git rev-parse --show-toplevel  # Find project root

Read {project_root}/.gitkkal/config.json. If not exists, use defaults and display once: "Using default settings. Run /gitkkal:init to customize."

2. Gather Change Information

Run in parallel:

git status --short          # All file states (NEVER use -uall flag)
git diff --cached           # Staged changes (actual content)
git diff                    # Unstaged changes (actual content)
git log --oneline -5        # Recent commit style reference

Commit candidates (analyze all together):

  • Staged changes (index)
  • Unstaged changes (modified tracked files)
  • Untracked files (new files)

3. Understand Semantic Intent

Focus on the "why" rather than the "what":

  • Read actual diff content, not just file statistics
  • Identify the semantic meaning of changes
  • Determine if changes represent: new feature, enhancement to existing feature, bug fix, refactoring, etc.
  • Ensure verb choice reflects intent: "add" = wholly new, "update" = enhancement, "fix" = bug fix

Read the full file on GitHub · 181 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. 2d ago First seen · 181 lines · 10 tokens per session scan A f3ef4edd0555

Subscribe to this mod's changes

commit is a command published in the GitHub repository BitYoungjae/marketplace (6 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 1,426 once invoked, about $0.0001 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-31.