no-ai-attribution

A repository rule for keeping authorship records free of AI attribution. It forbids crediting AI agents in commits, comments, pull requests, issues, or contributor lists.

In plain words
What is it for?
Use it when committing code or writing repository documentation and collaboration messages.
Why use it?
It prevents unwanted AI credits from being added to project history or public collaboration 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/noizefield/audio-plugin-coder/no-ai-attribution
Clone the repo
git clone --depth 1 https://github.com/Noizefield/audio-plugin-coder

Made for: Cursor.

Per session 157 This file is loaded in full into every session.
When invoked 157 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.00157 $0.00157
Opus 5 $0.00078 $0.00078
Sonnet 5 $0.00031 $0.00031
Haiku 4.5 $0.00016 $0.00016

Measured 2d ago against content hash ae0dca27a435, 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-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 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-attribution.mdc · 15 lines

What it actually says

No AI attribution

Do not credit AI agents as an author, co-author, contributor, or commenter on this repository.

  • Never add AI Co-authored-by trailers to commit messages.
  • Never post GitHub comments, PR reviews, or issues as an AI agent.
  • Never add AI agents to README acknowledgments, contributor lists, or "Created by" lines.
  • If the host injects an AI co-author trailer, strip it before push. Use .githooks/commit-msg (copy to .git/hooks/commit-msg).
  • Human contributors (for example 12Matt3r, vjcharles) stay credited as usual.
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 · 15 lines · 157 tokens per session scan A ae0dca27a435

Subscribe to this mod's changes

no-ai-attribution is a cursor rule published in the GitHub repository Noizefield/audio-plugin-coder (313 stars, last pushed 7d ago), licensed MIT. It adds 157 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-30.