pn-no-cursor-commit-trailers

A repository rule that prevents Cursor IDE attribution lines from being added to Git commit messages. Git commit messages describe changes recorded in a project's version history.

In plain words
What is it for?
Use it when creating or editing commits in repositories where Cursor-generated attribution lines must not appear.
Why use it?
It keeps commits free of unwanted Made-with or Co-authored-by Cursor trailers and provides a hook-based way to enforce that preference.

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/perniemann/pncore/pn-no-cursor-commit-trailers
Clone the repo
git clone --depth 1 https://github.com/perniemann/pnCore

Made for: Cursor.

Per session 166 This file is loaded in full into every session.
When invoked 166 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.00166 $0.00166
Opus 5 $0.00083 $0.00083
Sonnet 5 $0.00033 $0.00033
Haiku 4.5 $0.00017 $0.00017

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

Security

Grade A, and why

pn-no-cursor-commit-trailers 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/pn-no-cursor-commit-trailers.mdc · 15 lines

What it actually says

No Cursor commit trailers

When you create commits, edit messages, or suggest git commit text (including multi-line bodies):

  • Do not include Made-with: Cursor or any line starting with Made-with:.
  • Do not add Co-authored-by: Cursor <[email protected]> or similar IDE-generated Co-authored-by trailers.
  • If the tool or environment inserts those lines, remove them before the commit is finalized.

Prefer this repo’s prepare-commit-msg hook (git config core.hooksPath .githooks). See docs/commits.md for CI and contributor notes.

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 · 15 lines · 166 tokens per session scan A 29b0f2b6e5c9

Subscribe to this mod's changes

pn-no-cursor-commit-trailers is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed 2d ago), licensed MIT. It adds 166 tokens to every session, about $0.0008 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-31.