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 Grid0723/skills --skill git-commit-guidegit clone --depth 1 https://github.com/Grid0723/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/grid0723/skills/git-commit-guide)<a href="https://agentmods.dev/skills/grid0723/skills/git-commit-guide"><img src="https://agentmods.dev/badge/skills/grid0723/skills/git-commit-guide/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/grid0723/skills/git-commit-guide"><img src="https://agentmods.dev/badge/skills/grid0723/skills/git-commit-guide.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.00048 | $0.00831 |
| Opus 5.5 | $0.00019 | $0.00332 |
| Sonnet 5.5 | $0.00010 | $0.00166 |
| Haiku 4.5 | $0.00005 | $0.00083 |
Grade A, and why
git-commit-guide 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-commit-guide
定义提交的时机和格式。项目专属的前缀约定（如 feat(backend): / feat(xxx):）由各项目 AGENTS.md 声明。
Leading Words
| 术语 | 定义 |
|---|---|
| 一个 commit 只做一件事 | 单次提交只包含一个逻辑变更，方便 review 和回退 |
| 小步快跑 | 完成一个小功能点立即提交，不攒着 |
| 自检门 | 提交前必须通过检查清单——lint、测试、变更范围 |
提交时机
| 时机 | 示例 |
|---|---|
| 完成一个小功能点 | "新增 ETF 数据获取器" |
| 修复一个 bug | "修复 K 线日期格式解析错误" |
| 重构一个模块 | "提取公共清洗逻辑为独立模块" |
信息格式（通用部分）
<type>: <简短描述>
- 变更点 1
- 变更点 2
| 类型 | 含义 |
|---|---|
feat |
新功能 |
fix |
Bug 修复 |
refactor |
重构（不改变功能） |
docs |
文档 |
chore |
构建/依赖/工具 |
test |
测试 |
style |
格式（不影响逻辑） |
项目专属前缀
前缀格式由各项目 AGENTS.md 声明。 例如：
- TDX 项目：
feat(xxx):单项目格式 - trading_assistant：
feat(backend):/feat(frontend):前后端区分
选择提交前缀时，优先匹配当前项目的 AGENTS.md 声明；无声明则使用通用类型（feat/fix/refactor 等）。
提交类型 → 版本号递增（SemVer 联动）
提交类型决定下一次发布时的版本号递增（见 changelog-guide 校验）：
| 提交类型 | SemVer 递增 |
|---|---|
feat |
次版本号 Y（新增向下兼容功能） |
fix |
修订号 Z（修复问题，不影响 API） |
feat!: / 含 BREAKING CHANGE |
主版本号 X（不兼容修改） |
refactor / docs / chore / style / test |
无版本递增（除非累计显著变更） |
!前缀表示破坏性变更——如feat!: 重命名 getPrice 为 fetchPrice。含不兼容修改的提交必须在 message 中标注，否则版本号无法正确递增。
提交前自检
在 git commit 之前：
- 变更是否只属于一个逻辑主题？
- 提交信息是否描述了"做了什么"和"为什么"？
- 项目 lint 是否通过？
- 是否遵守了
git-guardrails的安全约束？ - 是否含不兼容修改？若是，已用
!或BREAKING CHANGE标注？ - 功能级变更是否需要同步更新 CHANGELOG（格式校验见
changelog-guide）？
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 · 75 lines · 48 tokens per session scan A 1dfdc6959541
git-commit-guide is a skill published in the GitHub repository Grid0723/skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 48 tokens to every session and 831 once invoked, about $0.0002 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
changelog
Auto-generate a changelog from git commits and sprint data. Internal and player-facing versions.
development-scheduler
A workflow for coordinating multi-role coding work through Herdr, a task scheduler, and repo-harness sessions. It assigns implementation, review, and handoff tasks while checking permissions and evidence.
git-commit
Generate conventional commit messages for Java projects. Use when user says "commit", "create commit", "commit changes", or after completing code changes that need to be committed.
conventional-commits
Use when uncommitted changes need to be split into atomic, conventional commits ordered for review. Triggers on "commit this", "make commits", "clean up commits", "commit the changes". In Hedgehog, each Loop step is already meant to be its own commit — this skill matters most when a Correction Protocol fast-forward…
pr-writing
Use whenever writing a PR title/description, a commit message body, a code review comment, or an issue — in Hedgehog's own repo or any consuming project. Triggers on "open a PR", "write the PR description", "comment on this PR", "file an issue". Covers writing style (terse, info-dense, Simplified Technical English)…
commit-changes
Stage, commit, and amend changes with conventional commit messages. Covers reviewing changes, selective staging, writing descriptive commit messages using HEREDOC format, and verifying commit history. Use when saving a logical unit of work to version control, creating a commit with a conventional message, amending the…