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/bookedsolidtech/discord-ops/003-attributiongit clone --depth 1 https://github.com/bookedsolidtech/discord-opsWrote 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/bookedsolidtech/discord-ops/003-attribution)<a href="https://agentmods.dev/rules/bookedsolidtech/discord-ops/003-attribution"><img src="https://agentmods.dev/badge/rules/bookedsolidtech/discord-ops/003-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 | $0.00323 | $0.00323 |
| Opus 5 | $0.00161 | $0.00161 |
| Sonnet 5 | $0.00065 | $0.00065 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
003-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 4d 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.
This is a copy
100% identical to 003-attribution — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
No AI Attribution in Client-Facing Content
Do not expose AI tooling in client git history, PR descriptions, or code comments.
What to remove
Remove these patterns from all commits, PR bodies, commit messages, and code:
Co-Authored-By: Claude Sonnet 4.6 <[email protected]>Co-Authored-By: Claude ...(any variant)Generated with Claude Code🤖 Generated with [Claude Code](https://claude.com/claude-code)claude.aireferences in commit messages or PR descriptions- AI assistant footers in PR templates
Enforcement
- commit-msg hook strips attribution automatically from every commit message
- This rule governs PR bodies and code comments, which the hook does not cover
- Before running
gh pr create, review the body — remove attribution strings manually
What's allowed
- Internal tooling notes in
.claude/config files (gitignored) - Documentation about the AI workflow in team-facing docs (e.g.,
CONTRIBUTING.md) when explicitly approved - Attribution in commits to internal/private BST repos where it's expected
Why
Client projects are delivered work product. AI tooling attribution in git history creates unnecessary disclosure, may violate NDA scope, and makes commits less professional. The work speaks for itself.
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.
- 4d ago First seen · 37 lines · 323 tokens per session scan A 213cd48005f1
003-attribution is a cursor rule published in the GitHub repository bookedsolidtech/discord-ops (4 stars, last pushed 1mo ago), licensed MIT. It adds 323 tokens to every session, about $0.0016 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to 003-attribution, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
git
Conventional commit message format for git commits.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
commit-sponsors
Every git commit message must acknowledge BetterDesk supporters.
git_workflow
Git Workflow and Configuration for AGB SDK.
conventional-commits
Use the Conventional Commit Messages specification to generate commit messages.
git-commits
description: "Reference and apply the git commits skill for Conventional Commit formatting and pre-push checks." alwaysApply: true.