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/duckplayergit 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/duckplayer)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/duckplayer"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/duckplayer.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.04965 |
| Opus 5 | $0.00000 | $0.02482 |
| Sonnet 5 | $0.00000 | $0.00993 |
| Haiku 4.5 | $0.00000 | $0.00496 |
Grade A, and why
duckplayer 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 — 763 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DuckPlayer Implementation Guide
Overview
DuckPlayer provides video playback within the app, separate from the web view-based player. The architecture separates concerns into distinct components using a presenter pattern, native UI views, and JavaScript integration for seamless video playback experiences.
Architecture Components
Core Architecture Pattern
DuckPlayer follows a presenter-driven architecture with clear separation of concerns:
// ✅ CORRECT - Presenter coordinates between components
final class DuckPlayerNativeUIPresenter {
private let navigationHandler: NativeDuckPlayerNavigationHandler
private let state: DuckPlayerState
private let pixelFiring: DuckPlayerPixelFiring
func presentPlayer(for videoID: String) {
// Coordinates pill presentation, player setup, and analytics
updateState(videoID: videoID)
configurePillType()
firePixels()
}
}
// ❌ INCORRECT - Don't manage all responsibilities in one view
struct DuckPlayerView: View {
@State private var videoID: String = ""
@State private var isPresented = false
// Don't handle navigation, state, and analytics directly in views
}
State Management Pattern
Use DuckPlayerState for centralized video state management:
// ✅ CORRECT - Centralized state management
final class DuckPlayerState {
var videoID: String?
var hasBeenShown: Bool = false
var timestamp: TimeInterval?
func reset() {
videoID = nil
hasBeenShown = false
timestamp = nil
}
}
// ❌ INCORRECT - Scattered state across components
struct DuckPlayerView: View {
@State private var videoID: String = ""
@State private var timestamp: TimeInterval = 0
// Don't duplicate state management
}
Component Responsibilities
DuckPlayerNativeUIPresenter
Role: Primary coordinator and state manager for the Native UI
Key Responsibilities:
- Manages presentation lifecycle of player UI components
- Coordinates between pill types (welcome, entry, re-entry)
- Handles user interactions and navigation events
- Manages constraint updates and visibility state
- Integrates with app navigation and browser features
- Handles orientation changes and UI adaptations
- Manages pixel firing for analytics tracking
- Controls toast notifications and dismiss count tracking
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 · 763 lines · 0 tokens per session scan A e12259030cb2
duckplayer 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 4,965 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.