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 iofold/ainative-claude-plugins --skill git-commit-helpergit clone --depth 1 https://github.com/iofold/ainative-claude-pluginsWrote 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/iofold/ainative-claude-plugins/git-commit-helper)<a href="https://agentmods.dev/skills/iofold/ainative-claude-plugins/git-commit-helper"><img src="https://agentmods.dev/badge/skills/iofold/ainative-claude-plugins/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/iofold/ainative-claude-plugins/git-commit-helper"><img src="https://agentmods.dev/badge/skills/iofold/ainative-claude-plugins/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.00071 | $0.01093 |
| Opus 5.5 | $0.00028 | $0.00437 |
| Sonnet 5.5 | $0.00014 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00109 |
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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Helper
Safe, chunked commits with best practices and sensitive file protection.
Workflow
Step 1: Analyze Current State
# Full status
git status --porcelain
# Staged changes
git diff --staged --stat
# Unstaged changes
git diff --stat
Step 2: Detect Sensitive Files (CRITICAL)
Before ANY commit, check for files that should NEVER be committed:
Sensitive patterns:
.env,.env.*(except.env.example)*.pem,*.key,*.p12,*.pfx,*.secretcredentials.json,secrets.json,secrets.yaml,token.jsonservice-account*.json,.npmrc,.pypirc
Temporary/Generated:
.tmp/,tmp/,*.log,*.cache,__pycache__/node_modules/,dist/,build/,.next/*.local(local config overrides)
Detection command:
git status --porcelain | grep -iE '\.(env|pem|key|secret|log|sqlite|db|local)$|credentials|secrets|token|\.tmp|node_modules|__pycache__|\.cache'
If sensitive files found:
- Unstage them:
git reset HEAD <file> - Check .gitignore:
cat .gitignore 2>/dev/null - Suggest additions:
.env .env.* !.env.example *.pem *.key *.secret .tmp/ *.log *.local - DO NOT proceed until resolved
Step 3: Group Changes into Chunks
Group related changes for atomic commits:
By type:
- Features: new files, new functions
- Fixes: modifications to existing logic
- Refactors: restructuring without behavior change
- Docs: README, comments, docs/
- Config: package.json, tsconfig, etc.
- Tests: test files with their implementations
Commands:
git diff --name-status
git diff --name-only | grep -E 'test|spec'
git diff --name-only | grep -E 'config|\.json$|\.yaml$'
Step 4: Commit with Proper Messages
Format (conventional commits):
<type>(<scope>): <description>
[body - explain WHY not just WHAT]
[footer - breaking changes, issue refs]
Types:
feat: New featurefix: Bug fixdocs: Documentationstyle: Formatting onlyrefactor: Code restructuretest: Testschore: Maintenance, deps
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 · 190 lines · 71 tokens per session scan A da108aef99e5
git-commit-helper is a skill published in the GitHub repository iofold/ainative-claude-plugins (3 stars, last pushed 1mo ago), licensed MIT. It adds 71 tokens to every session and 1,093 once invoked, about $0.0003 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 skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage automatic Git syncing on macOS with repo-sync. Use only when the user explicitly invokes /repo-sync.
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
git-commit-writer
Trigger when the user asks to write a commit message, generate a commit from staged changes, review a diff before committing, or says "/commit". Reads git diff --staged and produces an opinionated, convention-matching commit message.