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 rules/toptalentcoder/cursor-awesomerules/commit-message-formatgit clone --depth 1 https://github.com/toptalentcoder/Cursor-AwesomeRulesWrote 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/rules/toptalentcoder/cursor-awesomerules/commit-message-format)<a href="https://agentmods.dev/rules/toptalentcoder/cursor-awesomerules/commit-message-format"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/commit-message-format.svg" alt="Measured on agentmods" 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.00147 | $0.00147 |
| Opus 5 | $0.00073 | $0.00073 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
commit-message-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 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.
This is a copy
100% identical to commit-message-format — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
-
Use the following commit message format: [optional scope]:
[optional body]
[optional footer(s)]
Where:
type: One of the following: fix, feat, build, chore, ci, docs, perf, refactor, revert, style, test
scope (optional): A noun describing a section of the codebase (e.g., fluxcd, deployment).
description: A brief summary of the change in present tense.
body (optional): A more detailed explanation of the change.
footer (optional): One or more footers in the specified format.
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 · 22 lines · 147 tokens per session scan A 719c523aa8f3
commit-message-format is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It adds 147 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to commit-message-format, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
git_workflow
Git Workflow and Configuration for AGB SDK.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.