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 TechDufus/oh-my-claude --skill git-commit-validatorgit clone --depth 1 https://github.com/TechDufus/oh-my-claudeWrote 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/techdufus/oh-my-claude/git-commit-validator)<a href="https://agentmods.dev/skills/techdufus/oh-my-claude/git-commit-validator"><img src="https://agentmods.dev/badge/skills/techdufus/oh-my-claude/git-commit-validator/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/techdufus/oh-my-claude/git-commit-validator"><img src="https://agentmods.dev/badge/skills/techdufus/oh-my-claude/git-commit-validator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00057 | $0.01913 |
| Opus 5.5 | $0.00023 | $0.00765 |
| Sonnet 5.5 | $0.00011 | $0.00383 |
| Haiku 4.5 | $0.00006 | $0.00191 |
Grade A, and why
git-commit-validator 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 — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Validator
This skill MUST be invoked whenever you are about to create a git commit. It handles the complete workflow and enforces commit message standards.
When This Skill Activates
Auto-invoke this skill when the user implies code should be committed:
| Category | Trigger Phrases |
|---|---|
| Explicit commit | "commit", "make a commit", "commit this" |
| Ship intent | "ship it", "send it" |
| Finalization | "wrap it up", "finalize this", "we're done", "that's it" |
| After implementation | When you complete work and there are uncommitted changes |
Key insight: If the user's intent results in git commit being run, this skill MUST be used first.
Do NOT run git commit without this skill.
Complete Commit Workflow
Step 1: Gather Context
git status # See what's changed
git diff HEAD # See all changes (staged + unstaged)
git log --oneline -5 # Recent commit style reference
Step 1.5: Handle No Changes
If git status --porcelain returns empty AND nothing is staged:
- Do not attempt to commit - there's nothing to commit
- Inform the user: "No changes to commit"
- Exit the workflow
This prevents errors from running git commit with nothing staged.
Step 2: Stage Changes
Default behavior - stage all changes:
git add -A
If user specifies --staged - skip staging, use only what's already staged.
If user gives instructions - follow them:
- "ignore the docs" → don't stage doc files
- "only the src folder" → stage selectively
Step 3: Analyze and Generate Message
Based on the diff, determine:
- Type: feat, fix, docs, refactor, test, chore, perf, ci, build, style, revert
- Scope (optional): module or area affected
- Description: concise, imperative mood, lowercase
- Body: see decision matrix below
Message Format:
<type>[optional scope]: <description>
[body - required for non-trivial changes]
[optional footer - breaking changes, issue refs]
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 · 261 lines · 57 tokens per session scan A eddc366ec1dd
git-commit-validator is a skill published in the GitHub repository TechDufus/oh-my-claude (174 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,913 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
re0-git
Rewrite a finished commit's message into a clean, handoff-ready form in your own log style, so git log alone tells the story. User-invoked: run it after a commit.
maestro-improve
Turn filed lessons into the smallest doctrine edit. Use when a Lead assigns improvement work for one target: group pending lessons, make one evidence-linked commit per target, return it for independent challenge, and process each accepted or rejected lesson without deleting history.
git-commit-push-pr
Commit, push, and open a PR with an adaptive, value-first description. Use when the user says "commit and PR", "push and open a PR", "ship this", "create a PR", "open a pull request", "commit push PR", or wants to go from working changes to an open pull request in one step. Also use when the user says "update the PR…
git-commit
Create a git commit with a clear, value-communicating message. Use when the user says "commit", "commit this", "save my changes", "create a commit", or wants to commit staged or unstaged work. Produces well-structured commit messages that follow repo conventions when they exist, and defaults to conventional commit…
setup-git-hooks
Configure two-stage git hooks (pre-commit + pre-push) for quality automation, with either pre-commit or lefthook as the hook manager. Use after bootstrap-project and setup-adrs, when adding quality gates to an existing project, or when standardizing quality automation.
hook-safety-review
Use when a hook is about to be enabled or modified -- a hook recipe proposed for activation, a pre/post-tool or lifecycle hook added to agent settings, a git pre-commit hook added to a repo, or a third-party hook snippet pasted in from outside.