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/documentation-macos-appgit 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/documentation-macos-app)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/documentation-macos-app"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/documentation-macos-app.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.00018 | $0.00580 |
| Opus 5 | $0.00009 | $0.00290 |
| Sonnet 5 | $0.00004 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
documentation-macOS-app 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
macOS App Documentation Rules
Applies to: macOS app articles under macOS/DuckDuckGo/Documentation.docc/
Focus
This directory contains app-level documentation for the macOS browser:
- How the macOS app integrates with packages
- macOS-specific architecture patterns
- Platform-specific implementations (system extensions, IPC, etc.)
- Feature coordination within the app
What Belongs Here
✅ DO document:
- macOS app architecture (Tab system, MainWindow, Coordinators)
- Integration with packages (how macOS uses TunnelController, UserScript, etc.)
- Platform-specific features (system extensions, VPN agent, menu bar)
- UI components (NavigationBar, Preferences, MenuSystem)
- macOS-specific patterns and best practices
❌ DON'T document:
- Package protocol APIs (those go in package docs)
- Protocol definitions (unless app-specific like BookmarkManager)
- Generic patterns that iOS also uses (those go in package docs)
Code Guidelines
Minimize inline code - Keep total to ~10-15 blocks across ALL articles:
- Prefer file references: "See
ClassName.swift" - Prefer architecture diagrams
- Link to package docs for API examples
- Only show code for truly unique app patterns
Cross-Referencing
Always link to package docs for API details:
For the TunnelController API, see `TunnelController` in the VPN package.
See <doc:UserScript> in BrowserServicesKit for protocol documentation.
Article Structure Template
# Feature Name
Brief overview of the macOS app feature.
## Overview
What this feature does in the context of the macOS app.
For the [Package] API, see `ProtocolName` in the [Package] package.
## Architecture
macOS-specific architecture:
- How components are organized
- Process boundaries (if any)
- Integration points
## Key Components
- Component descriptions with DocC type references (e.g. ``ClassName``) or bare filenames — not full folder paths
- macOS-specific implementations
- File references, not code blocks
## Common Tasks
How to work with this feature in the macOS app:
- Brief procedural descriptions
- File references
- Link to package docs for API usage
## Related Topics
- Links to other app docs
- Links to package docs
- Links to related features
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 · 95 lines · 18 tokens per session scan A 46ca162cc06e
documentation-macOS-app is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (252 stars, last pushed 2d ago), licensed Apache-2.0. It adds 18 tokens to every session and 580 once invoked, about $0.0001 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.