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/sundegan/agent-skills/git-commitnpx skills add sundegan/agent-skills --skill git-commitgit clone --depth 1 https://github.com/sundegan/agent-skillsWhat 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.00055 | $0.00977 |
| Opus 5 | $0.00028 | $0.00489 |
| Sonnet 5 | $0.00011 | $0.00195 |
| Haiku 4.5 | $0.00006 | $0.00098 |
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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit
Goal
Create a clean Git commit for the current task. Include only changes that are related to the user's request and the work Agent performed in the current context, then use a mainstream Conventional Commits message in concise, direct English. For larger changes, include a short commit body with a bullet summary of the main code changes.
Workflow
- Confirm the repository root with
git rev-parse --show-toplevel. - Inspect the current Git state:
- Run
git status --short. - Check staged changes with
git diff --cached --statandgit diff --cached. - Check unstaged changes with
git diff --statand inspect relevant diffs. - Check untracked files with
git ls-files --others --exclude-standard.
- Run
- Determine what should be committed:
- Treat the current conversation, user request, and files Codex edited for that task as the primary commit boundary.
- If the user named files, paths, or a scope, commit only those changes.
- If the user simply says "commit", "提交", or similar, commit the changes related to the current task, not every dirty file in the repository.
- Commit all dirty files only when the user explicitly asks to commit everything/all changes, and still exclude secrets, local config, dependency caches, logs, and unsupported build artifacts.
- If changes were already staged before this request, verify whether they belong to the current task before including them. Unstage unrelated staged changes if needed, without discarding their content.
- If the worktree contains unrelated or ambiguous changes, ask before staging them.
- Stage the intended files with explicit paths whenever possible. Avoid broad staging commands when unrelated changes are present.
- Re-check
git status --shortandgit diff --cached --statbefore committing. - Compose an English Conventional Commits message:
- Use
<type>(<scope>): <summary>when a clear scope exists. - Use
<type>: <summary>when no concise scope is obvious. - Keep the subject under 72 characters when practical.
- Use imperative, present-tense English.
- Do not end the subject with a period.
- Use
- Add a commit body only when the change is large, multi-part, or not obvious from the subject:
- Leave a blank line after the subject.
- Add
Summary:followed by concise bullets. - Each bullet should describe a concrete code change or user-visible behavior.
- Run
git commitwith the prepared message. - Verify the result with
git status --shortandgit log -1 --pretty=fuller --stat.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 94 lines · 55 tokens per session scan A d4165e79cc76
git-commit is a skill published in the GitHub repository sundegan/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 55 tokens to every session and 977 once invoked, about $0.0003 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-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
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…