no-ai-coauthors

A repository rule that keeps Git commits credited only to the human developer. Git commits are saved records of changes to a code project.

In plain words
What is it for?
Applying human-only authorship when creating commits or suggesting commit messages in coding-agent tools.
Why use it?
It prevents AI tools or bots from being listed as co-authors or commit authors.

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/aksoftcode/aicrew/no-ai-coauthors
Clone the repo
git clone --depth 1 https://github.com/AKSoftCode/aicrew

Made for: Cursor.

Per session 140 This file is loaded in full into every session.
When invoked 140 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.00140 $0.00140
Opus 5 $0.00070 $0.00070
Sonnet 5 $0.00028 $0.00028
Haiku 4.5 $0.00014 $0.00014

Measured 2d ago against content hash 0ee04cee511a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

no-ai-coauthors 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 2d 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.

.cursor/rules/no-ai-coauthors.mdc · 16 lines

What it actually says

Commit attribution (human only)

When creating git commits (including suggested commit messages):

  • Never add Co-authored-by: trailers naming Cursor, Cursor Agent, Claude, Codex, Gemini, OpenAI, Anthropic, or any AI agent or bot.
  • Never set commit author or committer to AI tool identities (e.g. [email protected]).
  • Attribute work only to the human developer using this repository.

Applies in Cursor, Codex, Claude Code, Gemini CLI, and any other agent harness.

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. 2d ago First seen · 16 lines · 140 tokens per session scan A 0ee04cee511a

Subscribe to this mod's changes

no-ai-coauthors is a cursor rule published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 2mo ago), licensed MIT. It adds 140 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-31.

Related

Other cursor rules, from other repositories

x-harness

Use only light, standard, deep. Do not use small, medium, large.

BrianNguyen29/x-harness · 1,105 tokens

ult-autoscaffold-content

Generate real starter content for a project's What-L2 (requirements) and How-L2 (architecture/conventions) CEP layers once ult-repo-layout has resolved their paths but found them empty — an honest, minimal, YAML-frontmatter-first overview document per layer for small/single targets, or graphify-informed per-module…

linkpranay-ai/context-engineering-protocol · 207 tokens

ult-onboarding-index

Discover CEP-managed content already present in a target repo (What/How layer docs, compiled guidelines, context packages, decision ledger) via existence checks against layout-slots-registry.yaml-resolved paths, then write one canonical root AGENTS.md onboarding index plus thin per-tool pointer stubs…

linkpranay-ai/context-engineering-protocol · 206 tokens

ult-cep-wizard

Launch a local, localhost-only browser wizard with two journeys — layout onboarding for a project with ult-repo-layout installed, initialized or not — guides an uninitialized or not-yet-discovered repo through Run Discover, then shows resolved layer/slot state through four labeled boxes and a directory picker, and…

linkpranay-ai/context-engineering-protocol · 164 tokens

project

Core project context for ai-context-kit.

ofershap/ai-context-kit · 648 tokens

ult-institutional-memory-distill

Distill decisions, reasoning, and rejected alternatives from PRs, design docs, and postmortems into the project's decisionledger, so ult-context-generate's trip-wire can surface institutional memory before new work quietly repeats settled ground. Do NOT use to query the ledger against new work or decide…

linkpranay-ai/context-engineering-protocol · 83 tokens