commit

A command that reviews the changes in a Git project and creates a structured commit message. Git is a system for recording versions of code.

In plain words
What is it for?
Use it before committing code to inspect staged, unstaged, and new files, choose a change type, and create a commit with a summary and explanation.
Why use it?
It helps you understand what will be committed and avoids vague or incomplete commit messages. It can also stage relevant files when nothing is staged.

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/jaan-mustafa/10x-team/commit
Clone the repo
git clone --depth 1 https://github.com/Jaan-Mustafa/10x-Team
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 698 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.00000 $0.00698
Opus 5 $0.00000 $0.00349
Sonnet 5 $0.00000 $0.00140
Haiku 4.5 $0.00000 $0.00070

Measured 2d ago against content hash c6d6e1d93a6c, 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 · 83 lines

How it starts

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

/commit — Smart Commit Message Generator

Analyze all staged and unstaged changes, then create a well-structured commit.

Steps

  1. Gather context — Run these commands to understand the full picture:

    • git status to see all changed, staged, and untracked files
    • git diff to see unstaged changes
    • git diff --cached to see staged changes
    • git log --oneline -5 to see recent commit style
  2. Analyze the changes — For each changed file, understand:

    • What was added, removed, or modified
    • The intent behind the change (feature, fix, refactor, docs, test, chore)
    • Whether multiple concerns are mixed (suggest splitting if so)
  3. Stage files — If nothing is staged, stage the relevant files by name. Never use git add -A or git add .. Skip files that look like secrets (.env, credentials, tokens).

  4. Write the commit message using this format:

    <type>(<scope>): <short summary>
    
    <body — what changed and why, not how>
    
    Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
    

    Types: feat, fix, refactor, docs, test, chore, style, perf, ci, build

    Rules:

    • Summary line: imperative mood, lowercase, no period, under 50 chars
    • Body: wrap at 72 chars, explain WHY not WHAT
    • If changes span multiple concerns, suggest separate commits
    • Match the project's existing commit style from git log
  5. Show the proposed commit message to the user and ask for confirmation before committing.

  6. Commit using a HEREDOC to preserve formatting:

    git commit -m "$(cat <<'EOF'
    <the message>
    EOF
    )"
    

Examples

feat(auth): add OAuth2 login flow

Users can now sign in with Google and GitHub. Session tokens
are stored in HTTP-only cookies per security requirements.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>
fix(api): prevent duplicate webhook deliveries

Race condition in the queue consumer caused the same event to
fire twice when processing lagged. Added idempotency key check.

Co-Authored-By: Claude Opus 4.6 (1M context) <[email protected]>

Read the full file on GitHub · 83 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 · 83 lines · 0 tokens per session scan A c6d6e1d93a6c

Subscribe to this mod's changes

commit is a command published in the GitHub repository Jaan-Mustafa/10x-Team (11 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 698 tokens. 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.