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/architecturegit 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/architecture)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/architecture"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/architecture.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.00000 | $0.00494 |
| Opus 5 | $0.00000 | $0.00247 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00049 |
Grade A, and why
architecture 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DuckDuckGo Browser Architecture Guidelines
Overall Architecture
- This is a multi-platform monorepo supporting iOS and macOS browsers
- Shared code lives in
SharedPackages/directory - Platform-specific code in
iOS/andmacOS/directories - Follow modular architecture with clear separation of concerns
Architecture Patterns
MVVM for SwiftUI Views
- Use MVVM pattern for all SwiftUI views
- ViewModels should conform to
ObservableObject - Use
@Publishedproperties for reactive updates - Keep ViewModels testable and free from UI concerns
Example:
class FeatureViewModel: ObservableObject {
@Published var state: FeatureState = .idle
private let service: FeatureServiceProtocol
init(service: FeatureServiceProtocol) {
self.service = service
}
}
Coordinator Pattern
- Use coordinators for navigation and flow control
- Main app flow managed by
MainCoordinator - Create feature-specific coordinators as needed
- Coordinators handle navigation logic, not views
Dependency Injection
- Use constructor injection for dependencies
- Define protocols for all dependencies
- Use
AppDependencyProviderfor shared dependencies - Keep dependencies explicit and testable
Code Organization
Feature-Based Structure
- Organize code by features, not layers
- Each feature should have its own folder containing:
- Views (SwiftUI/UIKit)
- ViewModels
- Services
- Models
- Tests
File Naming Conventions
- ViewModels:
FeatureNameViewModel.swift - Views:
FeatureNameView.swift(SwiftUI) orFeatureNameViewController.swift(UIKit) - Services:
FeatureNameService.swift - Protocols:
FeatureNameProtocol.swiftor embed in main file
Extension Organization
- Split large classes into focused extensions
- Name extensions descriptively:
MainViewController+Email.swift - Group related functionality in extensions
Privacy-First Design
- All features must consider privacy implications
- Use secure storage for sensitive data
- Implement proper data clearing mechanisms
- Follow fireproofing patterns where applicable
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 · 77 lines · 0 tokens per session scan A 55d7a330ab07
architecture is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (252 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 494 tokens. 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.