27-commit-messages

27-commit-messages is a cursor rule for Cursor from Joaonic/agentkit. It costs 336 tokens per session, scanned A, original, MIT.

Rules for writing Git commit messages in a consistent format, with a GitLab issue number when the change is tied to a tracked issue. A commit is a saved change in Git.

In plain words
What is it for?
Use them when creating commits for features, fixes, tests, documentation, refactoring, performance work, or other changes in a GitLab project.
Why use it?
They make commits easier to search and connect to the work they implement.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit Use them when creating commits for features, fixes, tests, documentation, refactoring, performance work, or other changes in a GitLab project.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/joaonic/agentkit/27-commit-messages
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.

Clone the repo
git clone --depth 1 https://github.com/Joaonic/agentkit

Made for: Cursor.

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

agentmods badge for 27-commit-messages

README.md
[![agentmods](https://agentmods.dev/badge/rules/joaonic/agentkit/27-commit-messages/github.svg)](https://agentmods.dev/rules/joaonic/agentkit/27-commit-messages)
Your own site
<a href="https://agentmods.dev/rules/joaonic/agentkit/27-commit-messages"><img src="https://agentmods.dev/badge/rules/joaonic/agentkit/27-commit-messages/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.

agentmods 80×15 button for 27-commit-messages

Your own site · 80×15
<a href="https://agentmods.dev/rules/joaonic/agentkit/27-commit-messages"><img src="https://agentmods.dev/badge/rules/joaonic/agentkit/27-commit-messages.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 336 This file is loaded in full into every session.
When invoked 336 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00336 $0.00336
Opus 5.5 $0.00134 $0.00134
Sonnet 5.5 $0.00067 $0.00067
Haiku 4.5 $0.00034 $0.00034

Measured 1mo ago against content hash 17cc92adbe0e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

27-commit-messages 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.

src/core/rules/27-commit-messages.mdc · 35 lines

What it actually says

Commits — Semântico + Issue

Regra obrigatória

Quando o trabalho estiver ligado a uma issue GitLab (fluxo normativo: planos, implement-plan, tarefas com issue criada), cada mensagem de commit deve:

  1. Usar prefixo semântico: feat, fix, chore, docs, test, perf, refactor, ci.
  2. Incluir o número da issue no formato tipo(#NNN): descrição quando houver issue rastreada.

Exemplos

Correto Incorreto
feat(#142): add tenant scoped audit log feat: add tenant scoped audit log
fix(#88): guard tenant scope on event listener fix(api): guard tenant scope (#88)
test(#201): cover auth session use case test(api): cover auth session mapper

Sem issue rastreada

  • Usar apenas prefixo semântico sem número: chore: bump Spring Boot to 3.4.
  • Preferir criar issue antes de implementar para manter rastreabilidade.

Várias issues

  • Preferir uma issue principal no assunto; demais no corpo do commit se necessário.

Exceções

  • Commits automáticos de release, merge commits e ajustes pontuais sem issue rastreada (evitar; preferir issue antes).
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. 1mo ago First seen · 35 lines · 336 tokens per session scan A 17cc92adbe0e

Subscribe to this mod's changes

27-commit-messages is a cursor rule published in the GitHub repository Joaonic/agentkit (2 stars, last pushed 5mo ago), licensed MIT. It adds 336 tokens to every session, about $0.0013 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-31.