commitlint

A set of rules for writing consistent Git commit messages, using a format such as `feat(auth): add login`.

In plain words
What is it for?
It helps label new features, bug fixes, documentation, tests, and other changes in a shared format.
Why use it?
It prevents unclear commit history and makes changes easier to group, review, and release.

Cursor rule for Cursor

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/quinnjr/google-mcp/commitlint
Clone the repo
git clone --depth 1 https://github.com/quinnjr/google-mcp

Made for: Cursor.

Per session 1,027 This file is loaded in full into every session.
When invoked 1,027 The same file — it is already loaded in full.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01027 $0.01027
Opus 5 $0.00513 $0.00513
Sonnet 5 $0.00205 $0.00205
Haiku 4.5 $0.00103 $0.00103

Measured 2d ago against content hash 8491c930ba64, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

commitlint 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.

.cursor/rules/commitlint.mdc · 158 lines

How it starts

The opening of the file, as written. The whole thing — 158 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Commitlint Rules

All commit messages must follow the Conventional Commits specification.

Commit Message Format

<type>(<scope>): <subject>

[optional body]

[optional footer(s)]

Structure Rules

Part Rule Example
type Required, lowercase feat, fix, docs
scope Optional, lowercase, in parentheses (auth), (calendar)
subject Required, lowercase start, no period at end add user authentication
body Optional, blank line after subject Detailed explanation
footer Optional, for breaking changes/issues BREAKING CHANGE:, Fixes #123

Allowed Types

Type Description Bumps
feat New feature Minor
fix Bug fix Patch
docs Documentation only -
style Code style (formatting, semicolons) -
refactor Code change that neither fixes nor adds -
perf Performance improvement Patch
test Adding/updating tests -
build Build system or dependencies -
ci CI/CD configuration -
chore Other changes (tooling, config) -
revert Reverts a previous commit -

Allowed Scopes (Project-Specific)

auth, drive, docs, sheets, calendar, gmail,
contacts, youtube, slides, tasks, server, types, deps

Rules

Header Rules

  • type-enum: Type must be one of the allowed types
  • type-case: Type must be lowercase
  • type-empty: Type cannot be empty
  • scope-case: Scope must be lowercase
  • subject-case: Subject must start with lowercase
  • subject-empty: Subject cannot be empty
  • subject-full-stop: Subject cannot end with period
  • header-max-length: Header max 100 characters

Body Rules

  • body-leading-blank: Body must have blank line before it
  • body-max-line-length: Body lines max 100 characters

Footer Rules

  • footer-leading-blank: Footer must have blank line before it
  • footer-max-line-length: Footer lines max 100 characters

Read the full file on GitHub · 158 lines

Changes

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.

  1. 2d ago First seen · 158 lines · 1,027 tokens per session scan A 8491c930ba64

Subscribe to this mod's changes

commitlint is a cursor rule published in the GitHub repository quinnjr/google-mcp (11 stars, last pushed 4d ago), licensed MIT. It adds 1,027 tokens to every session, about $0.0051 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.