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.
git clone --depth 1 https://github.com/kuku0922/awesome-ai-coding-enhanceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/kuku0922/awesome-ai-coding-enhance/git-commit)<a href="https://agentmods.dev/commands/kuku0922/awesome-ai-coding-enhance/git-commit"><img src="https://agentmods.dev/badge/commands/kuku0922/awesome-ai-coding-enhance/git-commit/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/kuku0922/awesome-ai-coding-enhance/git-commit"><img src="https://agentmods.dev/badge/commands/kuku0922/awesome-ai-coding-enhance/git-commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00035 | $0.02858 |
| Opus 5.5 | $0.00014 | $0.01143 |
| Sonnet 5.5 | $0.00007 | $0.00572 |
| Haiku 4.5 | $0.00003 | $0.00286 |
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Command: Smart Git Commit with Message Options
This command works without any package manager/build tools, using only Git to automatically analyze changes and generate optimized commit messages with three distinct options:
🎯 Three Commit Message Options
-
Concise Version (Recommended) 🌟
- Brief, clear summary of changes
- Includes essential context and motivation
- Perfect for daily development workflow
-
Detailed Version 📋
- Comprehensive technical description
- Includes implementation details and rationale
- Ideal for complex features or critical fixes
-
Minimalist Version ⚡
- Single-line summary for quick submission
- Perfect for routine changes or hotfixes
- Maintains clarity while maximizing speed
The command will:
- Read changes (staged/unstaged)
- Determine if changes should be split into multiple commits
- Generate all three message options for user selection
- Support auto-selection with
--auto-selectflag - Execute
git addandgit commitas needed (runs local Git hooks by default; use--no-verifyto skip)
Usage
# Interactive mode - shows all three options
/git-commit
/git-commit --all # Stage all changes first
/git-commit --emoji # Include emoji in all options
/git-commit --no-verify # Skip Git hooks
# Auto-selection modes
/git-commit --auto-select concise # Auto-select concise version
/git-commit --auto-select detailed # Auto-select detailed version
/git-commit --auto-select minimalist # Auto-select one-line summary
# Advanced options
/git-commit --scope ui --type feat --emoji
/git-commit --amend --signoff
Options
Core Options
--auto-select <type>: Automatically select a message type without promptingconcise: Brief, clear summary (recommended)detailed: Comprehensive technical descriptionminimalist: Single-line summary for speed
--no-verify: Skip local Git hooks (pre-commit/commit-msgetc.).--all: When staging area is empty, automaticallygit add -Ato include all changes.--amend: Amend the last commit without creating a new one.--signoff: AddSigned-off-byline (use when following DCO process).--emoji: Include emoji prefix in commit message (applies to all three options).--scope <scope>: Specify commit scope (e.g.,ui,docs,api).--type <type>: Force commit type (e.g.,feat,fix,docs).
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.
- 1mo ago First seen · 294 lines · 0 tokens per session scan A 0c9e992b1494
git-commit is a command published in the GitHub repository kuku0922/awesome-ai-coding-enhance (3 stars, last pushed 10mo ago), licensed MIT. It adds 35 tokens to every session and 2,858 once invoked, about $0.0001 per session on Opus 5.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.
Other commands, from other repositories
undo-commit
Soft-undo the last commit. Restores its changes as staged, leaves working tree intact. Refuses if HEAD is already pushed to a tracked remote.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
commit
Stage, commit, and optionally ship further. Pass an escalation token (push, pr, merge, squash, squash merge) to skip the prompt. With no token, commits then asks how far to ship. Delegates message format to the atomic-git-discipline skill.
simplify-transform
Apply verified simplifications with user approval. Part of simplify- family.
fix-tests-execute
Phase 2 of fixing-tests: Fix Execution - investigate, classify, fix, verify, and commit each work item.
branch-commit
Return a branch name and concise commit message (max 3 lines) for the current task, grounded in the real git diff; with --apply, create the commit after showing the staged diff. Use when the user only needs quick branch and commit naming before committing, PR packaging is unnecessary, and a real diff exists; use…