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 niels-emmer/myace --skill commit-formatgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/commit-format)<a href="https://agentmods.dev/skills/niels-emmer/myace/commit-format"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/commit-format/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/niels-emmer/myace/commit-format"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/commit-format.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.00018 | $0.00439 |
| Opus 5 | $0.00009 | $0.00219 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
Commit Format 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 9d 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
Purpose
Give every commit a consistent, scannable shape so git log stays readable without requiring a full commit-message ceremony.
When to use it
Every time you make a commit. This applies whether you're committing after every small step or batching a few related changes together.
Format
<type>: <short imperative summary>
<optional body — the "why", if it's not obvious from the summary>
Common types:
feat:— new user-facing functionalityfix:— bug fixchore:— dependency bumps, config, tooling, cleanup with no behavior changedocs:— documentation only
Keep the summary line imperative ("add retry logic", not "added" or "adds") and short — aim for under ~65 characters so it doesn't wrap in most git tools. If the change needs more explanation than that, put it in the body as a sentence or two, not the summary.
Guidelines
- One logical change per commit where practical — makes it easy to revert just the part that turns out wrong.
- Don't bother with a body for genuinely self-explanatory commits ("fix: correct off-by-one in pagination" needs no further explanation).
- Do add a body when the "why" isn't obvious from the diff alone — e.g. working around a library bug, a deliberate tradeoff, or a non-obvious edge case being fixed.
- Avoid vague summaries like "update stuff" or "fixes" — they're useless six months later.
Expected output
A commit message that reads clearly on its own in git log --oneline, with enough of a body (when needed) that someone skimming history later understands the reasoning without re-reading the diff.
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.
- 9d ago First seen · 43 lines · 18 tokens per session scan A 8fe7b1c24a32
Commit Format is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 5d ago), licensed MIT. It adds 18 tokens to every session and 439 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
loom-git-workflow
Git operations guidance including branching strategies, commit conventions, merge workflows, conflict resolution, and worktree management.
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, splitting uncommitted work in a messy working tree into clean atomic commits, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple…
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
comet-safe-delivery
A Chinese-language procedure for safely delivering specified Comet changes through Git. It covers checking worktrees and unrelated edits, staging exact files, validating hooks, and authorized commits or pushes.
manuscript-as-code
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'finalv7' chaos and ensures submission-ready artifacts.
ac-commit-manager
Manage git commits for autonomous coding. Use when committing feature implementations, creating descriptive commits, managing git workflow, or handling version control.