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 skills/ghostship25/skilllint/git-commit-helpernpx skills add ghostship25/Skilllint --skill git-commit-helpergit clone --depth 1 https://github.com/ghostship25/SkilllintWhat 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.00029 | $0.00473 |
| Opus 5 | $0.00015 | $0.00236 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
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 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.
What it actually says
What this skill does
Given a staged git diff (git diff --staged), this skill drafts a commit
message following the Conventional Commits format (feat:, fix:, docs:,
refactor:, chore:, etc.), and flags when a diff mixes unrelated concerns
that should probably be split into multiple commits.
Usage
- Run
git diff --stagedand read the output. - Identify the primary type of change (feature, fix, refactor, docs, chore).
- Draft a subject line under 72 characters in the imperative mood (e.g. "Add retry logic to upload handler", not "Added" or "Adds").
- If the diff touches more than one unrelated area (e.g. a bugfix AND a new
feature), suggest splitting into separate commits with
git add -p. - For breaking changes, add a
BREAKING CHANGE:footer explaining the impact.
Example
Given a diff that adds retry logic to an HTTP client:
feat(http-client): add exponential backoff retry logic
Requests that fail with a 5xx status now retry up to 3 times with
exponential backoff before surfacing an error to the caller.
Notes
- Never fabricate a commit message for changes you haven't actually seen — always read the diff first.
- If the user hasn't staged anything, suggest
git addbefore drafting a message rather than guessing at intent. - Keep subject lines under 72 characters; wrap body text at ~72 columns.
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 · 51 lines · 29 tokens per session scan A d626089f7e9c
git-commit-helper is a skill published in the GitHub repository ghostship25/Skilllint (2 stars, last pushed 16d ago), licensed MIT. It adds 29 tokens to every session and 473 once invoked, about $0.0001 per session on Opus 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
git-workflow
Safe Git branch workflow — feature branches, rebase vs merge vs squash, interactive rebase, force-with-lease, reflog recovery, destructive-command guardrails.
git-expert
你是一个 Git 专家，擅长解决复杂的版本控制问题、优化工作流和处理团队协作场景。.
git-essentials
Expert Git workflow assistance for branching, merging, rebasing, conflict resolution, and history management. Use when working with Git operations beyond simple commits.
git-workflow
Git 워크플로우 - 커밋 전략, 브랜치 관리, 히스토리 정리.
git-workflow-management
Git workflow automation skill for commit message generation, branch management, pre-commit checks, and change history analysis.
sql-reporting
Conventions and review steps for writing analytics SQL against the warehouse. Use whenever the task involves querying tables, building a report, or aggregating metrics.