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/cdbattags/ai/deduplicate-rulesgit clone --depth 1 https://github.com/cdbattags/aiWhat 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.00330 | $0.00330 |
| Opus 5 | $0.00165 | $0.00165 |
| Sonnet 5 | $0.00066 | $0.00066 |
| Haiku 4.5 | $0.00033 | $0.00033 |
Grade A, and why
deduplicate-rules 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
Deduplicate User vs Project Rules
When creating or modifying a user-level rule (~/.cursor/rules/*.mdc), always check for overlapping project-level rules (.cursor/rules/*.mdc in the workspace).
Workflow
- Before writing a user-level rule, scan the current workspace's
.cursor/rules/for rules covering the same topic. - If overlap is found, warn the user:
- Name the overlapping project-level rule file
- Explain what it covers vs what the new user-level rule covers
- Ask whether to delete the project-level rule
- If the user confirms, delete the project-level rule.
- If the user declines, leave both but note the overlap in the user-level rule with a comment.
What Counts as Overlap
- Same topic (e.g., both about "no sleep commands")
- Subset coverage (project rule is a subset of the broader user rule)
- Conflicting guidance (project rule says X, user rule says Y)
Example
Creating user rule: ~/.cursor/rules/no-sleep-process-monitoring.mdc
Found overlapping project rule:
.cursor/rules/no-sleep-commands.mdc
(covers the same topic: avoiding sleep in shell commands)
The user-level rule supersedes the project-level one.
Delete .cursor/rules/no-sleep-commands.mdc? [ask user]
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 · 38 lines · 330 tokens per session scan A aeee23a2f831
deduplicate-rules is a cursor rule published in the GitHub repository cdbattags/ai (4 stars, last pushed 6mo ago), licensed MIT. It adds 330 tokens to every session, about $0.0016 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
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
09-android-best-practices
Android engineering best practices.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.
13-updating-project
Workflow for updating an existing project - dependency and SDK upgrades, migrations, refactors, bug fixes.