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.
npx agentmods add rules/yashvanthange/supermemory/no-cursor-attributiongit clone --depth 1 https://github.com/YashvantHange/SuperMemoryWhat 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 | $0.00121 | $0.00121 |
| Opus 5 | $0.00060 | $0.00060 |
| Sonnet 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 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.
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.
- 2d 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 2mo ago), licensed MIT. It adds 121 tokens to every session, about $0.0006 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
using-archipy-services
ArchiPy app services — thin transport, AppUtils, uvicorn via FastAPIConfig.
cursorrules
When the user asks you to implement a feature or fix an issue, use mooquickstart to atomically create and claim the task in a single step with complete specifications.
mcp-server
MCPサーバー実装に関するガイドライン.
agentmemory
AgentMemory MCP server rules — use addmemory before answering any question that introduces a project-specific convention, dependency, or constraint.
avos-agent-workflow
Avos memory workflow for AI coding agents. Guides codebase search and history lookup.
rust-cargo
Rust Cargo and Dependency Management Best Practices.