git-commit

A rule applied automatically when creating Git commits. It requires commit messages to omit the Co-authored-by line.

In plain words
What is it for?
Use it in projects where commit messages must not include Co-authored-by entries. It applies when the agent runs git commit.
Why use it?
It prevents unwanted attribution lines from being added to commit messages. This keeps commits aligned with the specified format.

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/asasugar/superspec/git-commit
Clone the repo
git clone --depth 1 https://github.com/asasugar/SuperSpec

Made for: Cursor.

Per session 132 This file is loaded in full into every session.
When invoked 132 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.00132 $0.00132
Opus 5 $0.00066 $0.00066
Sonnet 5 $0.00026 $0.00026
Haiku 4.5 $0.00013 $0.00013

Measured yesterday against content hash f9fe6de04ec2, 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 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.mdc · 34 lines

What it actually says

Git Commit 规则

禁止 Co-authored-by

执行 git commit 时,禁止在 commit message 中添加 Co-authored-by 行。

提交格式示例:

git commit -m "$(cat <<'EOF'
feat: 功能描述

EOF
)"

❌ 禁止:

feat: 功能描述

Co-authored-by: Cursor <[email protected]>

✅ 正确:

feat: 功能描述
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. yesterday First seen · 34 lines · 132 tokens per session scan A f9fe6de04ec2

Subscribe to this mod's changes

git-commit is a cursor rule published in the GitHub repository asasugar/SuperSpec (15 stars, last pushed 5mo ago), licensed MIT. It adds 132 tokens to every session, about $0.0007 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.