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 YangsonHung/awesome-agent-skills --skill git-commit-onlygit clone --depth 1 https://github.com/YangsonHung/awesome-agent-skillsWrote 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/yangsonhung/awesome-agent-skills/git-commit-only)<a href="https://agentmods.dev/skills/yangsonhung/awesome-agent-skills/git-commit-only"><img src="https://agentmods.dev/badge/skills/yangsonhung/awesome-agent-skills/git-commit-only/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/yangsonhung/awesome-agent-skills/git-commit-only"><img src="https://agentmods.dev/badge/skills/yangsonhung/awesome-agent-skills/git-commit-only.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.00074 | $0.01247 |
| Opus 5.5 | $0.00030 | $0.00499 |
| Sonnet 5.5 | $0.00015 | $0.00249 |
| Haiku 4.5 | $0.00007 | $0.00125 |
Grade A, and why
git-commit-only 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Only
Overview
Create one focused local Conventional Commit from the current repository's staged or requested changes without pushing to any remote.
The default output is one commit on the current branch. Analyze the actual diff, stage the requested change set, generate the commit message from the change content, and write a segmented body for non-trivial changes so reviewers can quickly see what changed by topic.
This workflow handles local commit requests only. It does not push, merge branches, rewrite history, create pull requests, or publish changes.
Conventional Commit Rules
Base format:
<type>[optional scope]: <description>
[body: optional only for trivial changes; required and segmented for non-trivial changes]
[footer(s): required for breaking changes; optional for relevant issue references]
For this skill, the body is optional only for trivial commits. For non-trivial changes, write a segmented body and include a Tests: or localized equivalent section when tests, validators, hooks, or manual verification ran.
Types:
| Type | Use for |
|---|---|
feat |
New user-facing or product capability |
fix |
Bug fix |
docs |
Documentation-only change |
style |
Formatting/style change with no logic impact |
refactor |
Code restructure with no feature or bug fix |
perf |
Performance improvement |
test |
Test-only or test coverage change |
build |
Build system, dependency, or packaging change |
ci |
CI or automation config change |
chore |
Maintenance or miscellaneous change |
revert |
Revert a previous commit |
Breaking changes:
- Use
!after the type or scope, such asfeat(api)!: remove legacy field. - Add a
BREAKING CHANGE:footer when the behavioral contract changes.
Message style:
- Use the repository's existing commit language.
- Write the subject in present tense and imperative mood, such as
fix login redirect. - Keep the subject under 72 characters when practical.
- Reference issues in the body or footer when relevant, such as
Closes #123orRefs #456.
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.
- 1mo ago First seen · 132 lines · 74 tokens per session scan A 3ffb7ae1d0a2
git-commit-only is a skill published in the GitHub repository YangsonHung/awesome-agent-skills (18 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,247 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-30.
Other skills, from other repositories
pr-squash-message
Generate one short Conventional Commits squash message describing only the net diff between the PR's base and head, set its header as the PR title, validate it with the repository's commitlint and both copy its description to the clipboard and display it, when asked for a squash message. Works in any Scenario…
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
branch-and-worktree-workflow
Isolates feature work in its own branch or worktree and integrates it cleanly when done. Use this when starting work that should not disturb the current workspace, when several efforts must proceed in parallel on one repository, or when implementation is finished and the change needs merging, rebasing, or splitting…
private-secret-scanning
Local Gitleaks scans for staged changes, push ranges, and full history in private repos, with redacted reports. Use to block committed secrets without GitHub Secret Protection.