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.
git clone --depth 1 https://github.com/quinnjr/google-mcpWrote 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/quinnjr/google-mcp/commitlint)<a href="https://agentmods.dev/rules/quinnjr/google-mcp/commitlint"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/commitlint/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/rules/quinnjr/google-mcp/commitlint"><img src="https://agentmods.dev/badge/rules/quinnjr/google-mcp/commitlint.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.01027 | $0.01027 |
| Opus 5.5 | $0.00411 | $0.00411 |
| Sonnet 5.5 | $0.00205 | $0.00205 |
| Haiku 4.5 | $0.00103 | $0.00103 |
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 1mo 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 — 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
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.
- 1mo ago First seen · 158 lines · 1,027 tokens per session scan A 8491c930ba64
commitlint is a cursor rule published in the GitHub repository quinnjr/google-mcp (11 stars, last pushed 1mo ago), licensed MIT. It adds 1,027 tokens to every session, about $0.0041 per session on Opus 5.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 cursor rules, from other repositories
conventional-commits
This rule defines the format for creating commit messages.
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
git
Git commit and branch rules that standardise how changes are described and organised. They also require explicit approval before committing code.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
commit-authorship
Git commits must be authored by the user only (no Cursor co-author).