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/duckduckgo/apple-browsers/anti-patternsgit clone --depth 1 https://github.com/duckduckgo/apple-browsersWrote 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/duckduckgo/apple-browsers/anti-patterns)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/anti-patterns"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/anti-patterns.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.02421 | $0.02421 |
| Opus 5 | $0.01210 | $0.01210 |
| Sonnet 5 | $0.00484 | $0.00484 |
| Haiku 4.5 | $0.00242 | $0.00242 |
Grade A, and why
anti-patterns 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.
How it starts
The opening of the file, as written. The whole thing — 388 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Anti-patterns and Common Mistakes to Avoid
Singleton Anti-patterns
❌ NEVER: Static Shared Instances Without Dependency Injection (.shared instance pattern)
Example: See singleton-antipattern.swift
❌ NEVER: Global State Access
// ❌ AVOID - Global state access
var globalSettings: [String: Any] = [:]
func someFunction() {
globalSettings["key"] = "value" // Global state is hard to test and debug
}
// ✅ CORRECT - Injected dependencies
final class SomeService {
private let settings: AppSettings
init(settings: AppSettings) {
self.settings = settings
}
func someFunction() {
settings.setValue("value", for: "key")
}
}
Async/Await Anti-patterns
❌ NEVER: UI Updates Without @MainActor
Example: See async-ui-updates.swift
❌ NEVER: Unhandled Async Errors
// ❌ AVOID - Swallowing async errors
func fetchData() async {
let data = try? await networkService.getData() // Silently ignoring errors
// Process data...
}
// ✅ CORRECT - Proper error handling
func fetchData() async throws {
let data = try await networkService.getData()
// Process data...
}
// Or handle errors appropriately:
func fetchData() async {
do {
let data = try await networkService.getData()
// Process data...
} catch {
// Log error and show user-friendly message
logger.error("Failed to fetch data: \(error)")
await showError(error)
}
}
❌ NEVER: Blocking Main Thread with Sync Operations
// ❌ AVOID - Blocking main thread
@MainActor
func loadData() {
let data = NetworkService.fetchDataSynchronously() // Blocks UI
updateUI(with: data)
}
// ✅ CORRECT - Use async operations
@MainActor
func loadData() async {
let data = try await NetworkService.fetchData() // Non-blocking
updateUI(with: data)
}
Memory Management Anti-patterns
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 · 388 lines · 2,421 tokens per session scan A 367a96b6a169
anti-patterns is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (252 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,421 tokens to every session, about $0.0121 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-09-01.
Other cursor rules, from other repositories
release-policy
Release, versioning, and signing policy for setmac.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.