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 agentmods add skills/godot-fun/godot-framework/git-commit-messagenpx skills add godot-fun/godot-framework --skill git-commit-messagegit clone --depth 1 https://github.com/godot-fun/godot-frameworkWhat 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 | $0.00044 | $0.00723 |
| Opus 5 | $0.00022 | $0.00362 |
| Sonnet 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 2d 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.
- 2d 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 2d ago), licensed MIT. It adds 44 tokens to every session and 723 once invoked, about $0.0002 per session on Opus 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…