git-commit-attribution

A rule for keeping Git commits under the human developer’s identity and excluding Cursor or agent co-authorship.

In plain words
What is it for?
Setting the author and committer before commits, then checking the latest commit’s attribution.
Why use it?
It prevents commits from being attributed to the wrong person or carrying unwanted co-author records.

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/eaststarai/sanad-agent/git-commit-attribution
Clone the repo
git clone --depth 1 https://github.com/EastStarAI/sanad-agent

Made for: Cursor.

Per session 254 This file is loaded in full into every session.
When invoked 254 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.00254 $0.00254
Opus 5 $0.00127 $0.00127
Sonnet 5 $0.00051 $0.00051
Haiku 4.5 $0.00025 $0.00025

Measured yesterday against content hash 6b7e6afc69d8, 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-attribution 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-attribution.mdc · 26 lines

What it actually says

Git Commit Attribution

When creating any git commit in this repository:

  1. Author and committer must be the repository developer only:
  2. Set identity explicitly for every commit (do not rely on Cursor defaults):
    git -c user.name="AhmedAttia3" -c user.email="[email protected]" commit -m "$(cat <<'EOF'
    ...
    EOF
    )"
    
  3. Never add Co-authored-by: Cursor, Co-authored-by: Cursor Agent, or any Cursor/agent trailer to commit messages.
  4. Before reporting a commit as done, verify attribution:
    git log -1 --format='author=%an <%ae> committer=%cn <%ce>%n%b'
    
    Reject and amend if any Cursor identity or Co-authored-by trailer is present.
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 · 26 lines · 254 tokens per session scan A 6b7e6afc69d8

Subscribe to this mod's changes

git-commit-attribution is a cursor rule published in the GitHub repository EastStarAI/sanad-agent (24 stars, last pushed yesterday), licensed MIT. It adds 254 tokens to every session, about $0.0013 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.