What is git-commit-standards?

Rules for writing consistent Git commit messages. Git is a tool that records changes to code, and a commit message briefly describes one recorded change.

Use them to check that commits use prefixes such as fix: or feat:, followed by a lowercase summary and a space, with the summary kept under the stated length.

A shared format makes project history easier to scan, search, and understand, while limiting message length keeps summaries concise.

git-commit-standards — Cursor rule by abderrahimghazali

Install

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.

agentmods

npx agentmods add rules/abderrahimghazali/cursor-rules/git-commit-standards

Clone the repo

git clone --depth 1 https://github.com/abderrahimghazali/cursor-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 411 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.00411
Opus 5	$0.00000	$0.00205
Sonnet 5	$0.00000	$0.00082
Haiku 4.5	$0.00000	$0.00041

Measured yesterday against content hash 428620d179ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

git-commit-standards 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 yesterday.

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.

.cursor/rules/git-commit-standards.mdc · 51 lines

What it actually says