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.
npx agentmods add commands/wangke19/gemini-ai-helpers/commit-suggestgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/commit-suggest)<a href="https://agentmods.dev/commands/wangke19/gemini-ai-helpers/commit-suggest"><img src="https://agentmods.dev/badge/commands/wangke19/gemini-ai-helpers/commit-suggest.svg" alt="Measured on agentmods" 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 | $0.00011 | $0.01129 |
| Opus 5 | $0.00005 | $0.00564 |
| Sonnet 5 | $0.00002 | $0.00226 |
| Haiku 4.5 | $0.00001 | $0.00113 |
Grade A, and why
commit-suggest 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.
This is a copy
100% identical to commit-suggest — 0 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.
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Name
git:commit-suggest
Synopsis
/git:commit-suggest # Analyze staged changes
/git:commit-suggest [N] # Analyze last N commits (1-100)
Description
AI-powered command that analyzes code changes and generates Conventional Commits–style messages.
Modes:
- Mode 1 (no argument) – Analyze staged changes (
git addrequired) - Mode 2 (with N) – Analyze last N commits to rewrite (N=1) or summarize for squash (N≥2)
Use cases:
- Create standardized commit messages
- Improve or rewrite existing commits
- Generate squash messages for PR merges
Difference from /git:summary – That command is read-only, while git:commit-suggest generates actionable commit message suggestions for user review and manual use.
Implementation
The command operates in two modes based on input:
Mode 1 (no argument):
- Collect staged changes via
git diff --cached - Analyze file paths and code content to identify type (feat/fix/etc.) and scope
- Generate 3 commit message suggestions (Recommended, Standard, Minimal)
- Display formatted suggestions and prompt user for selection
- Ask: "Which suggestion would you like to use? (1/2/3 or skip)"
- Support responses:
1,use option 2,commit with option 3,skip - Execute
git commitwith selected message if user requests
Mode 2 (with N):
- Retrieve last N commits using
git log - Parse commit messages to extract types, scopes, and descriptions
- For N=1: Suggest improved rewrite
For N≥2: Merge commits intelligently by type priority (
fix > feat > perf > refactor > docs > test > chore) - Generate 3 commit message suggestions (Recommended, Standard, Minimal)
- Display formatted suggestions and prompt user for selection
- Ask: "Which suggestion would you like to use? (1/2/3 or skip)"
- Support responses:
1,use option 2,amend with option 3,skip - Execute
git commit --amend(N=1) or squash operation (N≥2) if user requests
Examples
# Generate message for staged files
git add src/auth.ts src/middleware.ts
/git:commit-suggest
# Rewrite last commit message
/git:commit-suggest 1
# Summarize last 5 commits for squash
/git:commit-suggest 5
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.
- yesterday First seen · 141 lines · 11 tokens per session scan A 2a381efe2bb2
commit-suggest is a command published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 11 tokens to every session and 1,129 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit-suggest, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
start-work
Begin work on a Jira issue - creates branch, sets up environment.
wtfp:contribute
Guide a bounded WTF-P contribution from branch creation through a reviewable change request.
yapper-commit
The /yapper-commit command generates a verbose, fully-explained Git commit message for the current change or a described change. The resulting commit message explains not just what changed, but why it changed, what problem it solves, and how the solution works — providing maximum context for future readers of the git…
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.
speckit.git.initialize
Initialize a Git repository with an initial commit.
speckit.git.commit
Auto-commit changes after a Spec Kit command completes.