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 hg-pyun/claude-code-marketplace --skill git-commitgit clone --depth 1 https://github.com/hg-pyun/claude-code-marketplaceWrote 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/hg-pyun/claude-code-marketplace/git-commit)<a href="https://agentmods.dev/skills/hg-pyun/claude-code-marketplace/git-commit"><img src="https://agentmods.dev/badge/skills/hg-pyun/claude-code-marketplace/git-commit/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/hg-pyun/claude-code-marketplace/git-commit"><img src="https://agentmods.dev/badge/skills/hg-pyun/claude-code-marketplace/git-commit.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.00183 | $0.01675 |
| Opus 5.5 | $0.00073 | $0.00670 |
| Sonnet 5.5 | $0.00037 | $0.00335 |
| Haiku 4.5 | $0.00018 | $0.00168 |
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 2mo 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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- User asks to commit current changes ("커밋해줘", "commit this", "save my work")
- User signals task completion and wants the work captured ("이거 저장해", "wrap this up")
- The user invokes
/git-commit - The working tree has staged or unstaged changes worth recording </Use_When>
<Do_Not_Use_When>
- User asks about commit history (
git logexploration) — answer directly - User explains what a commit is or asks about commit conventions conceptually
- The working tree is clean — there is nothing to commit
- User wants a merge commit or revert (out of scope for this skill) </Do_Not_Use_When>
<Why_This_Exists>
Conventional commits are valuable but tedious to write by hand, especially when one logical change spans many files. This skill reads the diff, picks the right type(scope), drafts a one-line subject and a body that explains the why, and executes the commit immediately. It also detects when a single commit would mash unrelated changes together and offers a split plan up front. Co-Authored-By trailers are blocked because they pollute commit history and many teams treat them as spam.
</Why_This_Exists>
<Execution_Policy>
- The subject line and body are written in
$LANGUAGE(default: Korean; overrideable via--lang=<value>). typeandscopekeywords remain English (e.g.,feat,fix,chore,refactor).- Execute the commit immediately after composing the message — do not ask for preview confirmation.
- NEVER include a
Co-Authored-Bytrailer or footer in any commit message. This rule overrides every other instruction. - Skip merge commits and revert commits — out of scope.
- Skip ticket/issue references in the commit body unless the user explicitly asked. </Execution_Policy>
<Settings_Reference>
$LANGUAGE: the language setting fromplugin.jsonsettings.language(defaultKorean). Override with--lang=<value>argument. Presets: Korean, English, Japanese, Chinese. Custom values (e.g.,Spanish,Bahasa Indonesia) are accepted as free text. </Settings_Reference>
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.
- 2mo ago First seen · 116 lines · 183 tokens per session scan A 9d7d2b43c390
git-commit is a skill published in the GitHub repository hg-pyun/claude-code-marketplace (2 stars, last pushed 4mo ago), licensed MIT. It adds 183 tokens to every session and 1,675 once invoked, about $0.0007 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.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
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…