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 7-e1even/learn-agent --skill git-commit-conventiongit clone --depth 1 https://github.com/7-e1even/learn-agentWrote 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/7-e1even/learn-agent/git-commit-convention)<a href="https://agentmods.dev/skills/7-e1even/learn-agent/git-commit-convention"><img src="https://agentmods.dev/badge/skills/7-e1even/learn-agent/git-commit-convention/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/7-e1even/learn-agent/git-commit-convention"><img src="https://agentmods.dev/badge/skills/7-e1even/learn-agent/git-commit-convention.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00418 |
| Opus 5.5 | $0.00013 | $0.00167 |
| Sonnet 5.5 | $0.00006 | $0.00084 |
| Haiku 4.5 | $0.00003 | $0.00042 |
Grade A, and why
git-commit-convention 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.
What it actually says
Git 提交规范
格式
<type>(<scope>): <subject>
<body>
<footer>
type必选，scope可选（改动涉及的模块/目录名），subject必选。- subject 用祈使句（"add" 不是 "added"），不加句号，不超过 50 字符。
- body 讲为什么改，不复述 diff 里能看到的"改了什么"。
- 一次提交只做一件事：重构和功能修改不混在同一个提交里。
type 怎么选
| type | 用于 |
|---|---|
| feat | 新功能（用户可感知的行为变化） |
| fix | 修 bug（引用 issue 编号写进 footer） |
| refactor | 不改行为的结构调整 |
| test | 只增改测试 |
| docs | 只改文档/注释 |
| chore | 构建、依赖、CI 等工程杂务 |
拿不准 feat 还是 fix：问"用户之前的预期是什么"——之前就该这样但没做到 = fix；之前没有这个预期 = feat。
footer
- 不兼容变更：以
BREAKING CHANGE:开头，说明迁移方法。 - 关联 issue：
Closes #123。
提交前自查
git diff --staged过一遍：有没有混进无关文件（调试代码、锁文件意外变更）？- 这个提交单独 revert 时，代码库还能编译/测试通过吗？不能 → 拆分方式有问题。
- subject 能让三个月后的自己一眼看懂吗？
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 · 46 lines · 32 tokens per session scan A 3f9d69f9da8c
git-commit-convention is a skill published in the GitHub repository 7-e1even/learn-agent (287 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 418 once invoked, about $0.0001 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
conventional-git
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…
adk-git
Writes commit messages and pull request descriptions for the adk-python repository: Conventional Commits types and scopes, subject lines that say why a change was made, and the linked-issue and testing-plan sections the PR template requires. Use when writing or rewording a commit message, squashing commits before a…
work
Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
oma-scm
Manage Git branches, merges, conflicts, commits, and release baselines. Use for repository history and change-management operations.
commit
Skill "commit" from clacky-ai/openclacky, covering smart commit skill, critical requirement: single-line commits only, core philosophy, usage and process steps.