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 godot-fun/godot-framework --skill git-commit-messagegit clone --depth 1 https://github.com/godot-fun/godot-frameworkWrote 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/godot-fun/godot-framework/git-commit-message)<a href="https://agentmods.dev/skills/godot-fun/godot-framework/git-commit-message"><img src="https://agentmods.dev/badge/skills/godot-fun/godot-framework/git-commit-message/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/godot-fun/godot-framework/git-commit-message"><img src="https://agentmods.dev/badge/skills/godot-fun/godot-framework/git-commit-message.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.00044 | $0.00723 |
| Opus 5.5 | $0.00018 | $0.00289 |
| Sonnet 5.5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
git-commit-message 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Commit Message
Quick Start
When the user needs a commit message:
- Inspect changes:
git status,git diff,git diff --staged - Read recent style:
git log --oneline -15 - Draft a single-line Conventional Commits message matching repo conventions
- Return the message only — do not commit unless explicitly asked
Run status, diff, and log in parallel when possible.
Message Format
Single line only — no body:
<type>[<scope>]: <subject>
| Part | Rules |
|---|---|
| type | Required. One of: feat, fix, refactor, docs, test, chore, perf, ci, build, style, revert |
| scope | Optional. Module or area in square brackets (e.g. [auth], [api], [ui]). Omit brackets entirely if unclear |
| subject | Imperative mood, lowercase, no trailing period, ≤72 chars. Must stand alone — pack intent into this line |
Never add a blank line or body paragraph after the subject.
Type Selection
| Type | When |
|---|---|
feat |
New user-facing capability |
fix |
Bug fix |
refactor |
Code change without behavior change |
docs |
Documentation only |
test |
Tests only |
chore |
Maintenance, deps, tooling |
perf |
Performance improvement |
ci |
CI/CD config |
build |
Build system or external deps |
style |
Formatting, whitespace (no logic change) |
revert |
Revert a prior commit |
Scope Guidelines
- Use existing scopes from recent commits when present
- Prefer short, stable names:
auth,db,config,deps - Drop scope rather than guess incorrectly
Workflow
Task Progress:
- [ ] Run git status + diff (+ staged diff if relevant)
- [ ] Read recent git log for style alignment
- [ ] Identify primary change type and scope
- [ ] Draft single-line subject (imperative, self-contained)
- [ ] Check for secrets or files that should not be committed
- [ ] Present message to user
Split vs Single Commit
- One logical change → one commit
- Unrelated changes (feat + fix in different areas) → suggest splitting
- Large refactor + feature → suggest separate commits
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 · 100 lines · 44 tokens per session scan A f28083d9b54b
git-commit-message is a skill published in the GitHub repository godot-fun/godot-framework (116 stars, last pushed 1mo ago), licensed MIT. It adds 44 tokens to every session and 723 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-30.
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.
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…
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.