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/solvapay/solvapay-sdkWrote 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/solvapay/solvapay-sdk/no-ai-attribution)<a href="https://agentmods.dev/rules/solvapay/solvapay-sdk/no-ai-attribution"><img src="https://agentmods.dev/badge/rules/solvapay/solvapay-sdk/no-ai-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/solvapay/solvapay-sdk/no-ai-attribution"><img src="https://agentmods.dev/badge/rules/solvapay/solvapay-sdk/no-ai-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.00147 | $0.00147 |
| Opus 5.5 | $0.00059 | $0.00059 |
| Sonnet 5.5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
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 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 AI attribution
Never add Cursor, any agent, or any AI tool as a commit or PR author.
- Do not add
Co-Authored-By: Cursor,Co-authored-by: Cursor <[email protected]>, or any other agent/toolCo-Authored-By - Do not add
Made-with: Cursor,Generated with Cursor, or similar trailers - Do not add "Generated with …", tool footers, or AI attribution in PR titles or bodies
- Commits and PRs are authored only by the human who asked for the change
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 · 14 lines · 147 tokens per session scan A 12db7abbdc95
no-ai-attribution is a cursor rule published in the GitHub repository solvapay/solvapay-sdk (5 stars, last pushed 6d ago), licensed MIT. It adds 147 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-09-10.
Other cursor rules, from other repositories
git
Git workflow — commit format, push policy, and PR process.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
no-ai-contributors
Never add AI tools as git authors or project contributors.
git-discipline
Commit, push, and branching rules. Owns ALL git behavior; other files state only their deviations.
git-commit-standards
Enforce structured Git commit messages.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.