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/YashvantHange/SuperMemoryWrote 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/yashvanthange/supermemory/no-cursor-attribution)<a href="https://agentmods.dev/rules/yashvanthange/supermemory/no-cursor-attribution"><img src="https://agentmods.dev/badge/rules/yashvanthange/supermemory/no-cursor-attribution/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/yashvanthange/supermemory/no-cursor-attribution"><img src="https://agentmods.dev/badge/rules/yashvanthange/supermemory/no-cursor-attribution.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.00121 | $0.00121 |
| Opus 5.5 | $0.00048 | $0.00048 |
| Sonnet 5.5 | $0.00024 | $0.00024 |
| Haiku 4.5 | $0.00012 | $0.00012 |
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 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
No Cursor commit attribution
When creating git commits in this repo:
- Never add
Co-authored-by: Cursor <[email protected]>to commit messages. - Never add
Made-with: Cursoror any other Cursor attribution trailer. - Do not use
git commit --trailerfor Cursor attribution. - Use only the user's identity as author.
- If a co-author line is required, use the label from
.git-coauthor(default: SuperMemory Agent).
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 · 15 lines · 121 tokens per session scan A cfe2f727277f
no-cursor-attribution is a cursor rule published in the GitHub repository YashvantHange/SuperMemory (2 stars, last pushed 4mo ago), licensed MIT. It adds 121 tokens to every session, about $0.0005 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-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.
git-commit-conventions
Cursor rule "git-commit-conventions" from brettdavies/cursor-template, covering commit message conventions, mandatory process sequence, 1. capture changes [required], 2. process diff file [required] and 3. generate commit message [required].
git-workflow
Step-by-step instructions for Git workflow, including branch management, commits, and PR process.
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.