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/roynertr/cobie-mcpWrote 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/roynertr/cobie-mcp/no-cursor-attribution)<a href="https://agentmods.dev/rules/roynertr/cobie-mcp/no-cursor-attribution"><img src="https://agentmods.dev/badge/rules/roynertr/cobie-mcp/no-cursor-attribution.svg" alt="Measured on agentmods" 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.00100 | $0.00100 |
| Opus 5 | $0.00050 | $0.00050 |
| Sonnet 5 | $0.00020 | $0.00020 |
| Haiku 4.5 | $0.00010 | $0.00010 |
Grade A, and why
no-cursor-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 7d 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
No Cursor Attribution
Never add Made-with: Cursor, Co-authored-by: Cursor, Co-authored-by: Cursor <[email protected]>, or any Cursor attribution/trailer to commits, pull requests, or code comments.
When creating commits or PRs, use only the user's git identity. Do not append agent trailers or co-author lines for Cursor.
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.
- 7d ago First seen · 11 lines · 100 tokens per session scan A 13b7a435126d
no-cursor-attribution is a cursor rule published in the GitHub repository roynertr/cobie-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 100 tokens to every session, about $0.0005 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.
Other cursor rules, from other repositories
git-commits
Apply when generating git commit messages, performing commits, pushing to remote, or suggesting commit-related changes. Enforces Conventional Commits format and pre-push CI verification.
conventional-commits
Enforce Conventional Commits format for all commit messages.
git-workflow
Vollagentische Entwicklung, Auto-Commits, Commit-Konventionen.
no-cursor-attribution
Git commits must not include Cursor co-author attribution.
development-workflow
Cursor rule "development-workflow" from floriscornel/todo-mcp, covering development workflow for todo mcp, testing & quality assurance, commit structure, branch & pr workflow and publication & releases.
git-auto-commit
This rule ensures that after Cursor IDE automatically performs changes from Git commits, the modified files are automatically committed back to Git using the conventional commit format. This maintains a clear and consistent commit history that explains what changes were made and why.