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 Pixel-Process-UG/superkit-agents --skill git-commit-helpergit clone --depth 1 https://github.com/Pixel-Process-UG/superkit-agentsWrote 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/pixel-process-ug/superkit-agents/git-commit-helper)<a href="https://agentmods.dev/skills/pixel-process-ug/superkit-agents/git-commit-helper"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/git-commit-helper/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/pixel-process-ug/superkit-agents/git-commit-helper"><img src="https://agentmods.dev/badge/skills/pixel-process-ug/superkit-agents/git-commit-helper.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.00058 | $0.02296 |
| Opus 5.5 | $0.00023 | $0.00918 |
| Sonnet 5.5 | $0.00012 | $0.00459 |
| Haiku 4.5 | $0.00006 | $0.00230 |
Grade A, and why
git-commit-helper 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Helper
Overview
Enforce conventional commit standards, guide semantic versioning decisions, generate changelogs, and ensure commit message quality. This skill provides a structured approach to version control communication that enables automated tooling and clear project history.
Phase 1: Analyze Changes
Analyze the staged diff to understand what was changed:
git diff --cached --stat
git diff --cached
- Identify the files and modules affected
- Determine the nature of the change (new feature, bug fix, refactoring, etc.)
- Check if the change is breaking (API changes, removed features, changed contracts)
STOP — Do NOT write a commit message until you understand the full scope of changes.
Phase 2: Classify and Compose
Commit Type Decision Table
| Type | When to Use | Version Bump | Example |
|---|---|---|---|
feat |
New feature for the user | MINOR | feat(auth): add OAuth2 login flow |
fix |
Bug fix for the user | PATCH | fix(api): handle null response in user endpoint |
docs |
Documentation only changes | None | docs(readme): update installation steps |
style |
Formatting, missing semicolons, etc. | None | style(lint): fix trailing whitespace |
refactor |
Code change with no behavior change | None | refactor(utils): extract date formatting helpers |
perf |
Performance improvement | PATCH | perf(query): add index for user lookup |
test |
Adding or correcting tests | None | test(auth): add login failure scenarios |
chore |
Maintenance, deps, tooling | None | chore(deps): update typescript to 5.4 |
ci |
CI/CD configuration changes | None | ci(github): add Node 20 to test matrix |
build |
Build system or external dependencies | None | build(webpack): optimize chunk splitting |
Conventional Commit Format
<type>(<scope>): <description>
[optional body]
[optional footer(s)]
Scope Guidelines
Scope should identify the area of the codebase affected:
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 · 277 lines · 58 tokens per session scan A abe6d373a98d
git-commit-helper is a skill published in the GitHub repository Pixel-Process-UG/superkit-agents (3 stars, last pushed 7mo ago), licensed MIT. It adds 58 tokens to every session and 2,296 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-09-03.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
shipping-and-launch
Prepares production launches. Use when preparing to deploy to production. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.
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.
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
git-ops
Close out a local coding task on the bound daemon — stage, commit, branch, merge, push via cloud git — and when a merge conflicts, STOP and escalate with the file list instead of auto-resolving. Push reaches only the bare replica; prod-triggering tags are refused.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.