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.
git clone --depth 1 https://github.com/AKSoftCode/aicrewWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/aksoftcode/aicrew/no-ai-coauthors)<a href="https://agentmods.dev/rules/aksoftcode/aicrew/no-ai-coauthors"><img src="https://agentmods.dev/badge/rules/aksoftcode/aicrew/no-ai-coauthors/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/aksoftcode/aicrew/no-ai-coauthors"><img src="https://agentmods.dev/badge/rules/aksoftcode/aicrew/no-ai-coauthors.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00140 | $0.00140 |
| Opus 5.5 | $0.00056 | $0.00056 |
| Sonnet 5.5 | $0.00028 | $0.00028 |
| Haiku 4.5 | $0.00014 | $0.00014 |
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 1mo 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.
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.
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.
- 1mo ago First seen · 16 lines · 140 tokens per session scan A 0ee04cee511a
no-ai-coauthors is a cursor rule published in the GitHub repository AKSoftCode/aicrew (3 stars, last pushed 3mo ago), licensed MIT. It adds 140 tokens to every session, about $0.0006 per session on Opus 5.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.
Other cursor rules, from other repositories
git-conventional-commit-messages
Cursor rules for Git development with conventional commit messages integration.
python-github-setup-cursorrules-prompt-file
Cursor rules for Python development with GitHub setup integration.
commit-message-generation-rule
Rules for writing consistent Git commit messages, using labels such as feat for a feature, fix for a bug, and docs for documentation. A commit message records one set of code changes.
atomic-commits
Git best practices - atomic commits, descriptive messages, feature branches.
quality-gates
Enforce quality checks before commits - lint, typecheck, and test affected code.
commit-message-format
A rule for writing Git commit messages in a standard format, such as `fix: correct login error` or `feat(api): add search`. A commit message records what a code change contains.