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 skills add richardcb/oh-my-gemini --skill git-commitgit clone --depth 1 https://github.com/richardcb/oh-my-geminiWrote 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/skills/richardcb/oh-my-gemini/git-commit)<a href="https://agentmods.dev/skills/richardcb/oh-my-gemini/git-commit"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/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/skills/richardcb/oh-my-gemini/git-commit"><img src="https://agentmods.dev/badge/skills/richardcb/oh-my-gemini/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.00043 | $0.01131 |
| Opus 5.5 | $0.00017 | $0.00452 |
| Sonnet 5.5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Skill
Goal
Generate meaningful, conventional commit messages by analyzing staged changes. Creates commits that tell a story and make git history useful.
Activation Triggers
- User says "commit", "git commit", or "save changes"
- User asks for a commit message
- After completing implementation tasks
Process
1. Check Git Status
# Check if in a git repo
git rev-parse --git-dir 2>/dev/null || echo "NOT_A_GIT_REPO"
# Check staged changes
git diff --cached --stat
# Check unstaged changes
git status --short
2. Analyze Staged Changes
# Get detailed diff of staged changes
git diff --cached
# Get list of files changed
git diff --cached --name-only
# Get change statistics
git diff --cached --shortstat
3. Categorize Changes
Determine the commit type based on changes:
| Type | Description | Examples |
|---|---|---|
feat |
New feature | New endpoint, new component, new capability |
fix |
Bug fix | Error handling, logic correction |
docs |
Documentation | README, comments, JSDoc |
style |
Formatting | Whitespace, semicolons, no logic change |
refactor |
Code restructuring | Rename, extract function, no behavior change |
perf |
Performance | Optimization, caching |
test |
Tests | New tests, test fixes |
chore |
Maintenance | Dependencies, build config |
ci |
CI/CD | GitHub Actions, deployment |
4. Identify Scope
Look at changed files to determine scope:
- Single component: Use component name as scope
- Multiple related files: Use feature/module name
- Many unrelated files: Consider splitting commit
5. Generate Commit Message
Format
<type>(<scope>): <subject>
<body>
<footer>
Subject Rules
- Max 50 characters
- Imperative mood ("add" not "added")
- No period at end
- Lowercase
Body Rules
- Wrap at 72 characters
- Explain what and why, not how
- Separate from subject with blank line
Footer Rules
- Reference issues:
Closes #123 - Breaking changes:
BREAKING CHANGE: description
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 · 206 lines · 43 tokens per session scan A a744556a6f86
git-commit is a skill published in the GitHub repository richardcb/oh-my-gemini (18 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 1,131 once invoked, about $0.0002 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-30.
Other skills, from other repositories
intuitive-squash
Safely rewrite noisy local history into reviewable commits, with aggressive or moderate plan choices, when the user explicitly asks to squash.
ship
Use when shipping code - complete workflow: merge main, run tests, multi-review with auto-fix, commit, push, create PR. Replaces manual commit-push-pr flows.
dev-updates
Detect and summarize uncommitted git changes grouped by feature area, then generate a structured commit message. Use when the user says "what's the update?", "what changed?", "summarize my changes", "what have I done?", or "what did I update?".
git-workflow
Git workflow patterns including branching strategies, commit conventions, merge vs rebase, conflict resolution, and collaborative development best practices for teams of all sizes.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.