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/pixel-definitionsgit 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/pixel-definitions)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/pixel-definitions"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/pixel-definitions.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.00022 | $0.03493 |
| Opus 5 | $0.00011 | $0.01747 |
| Sonnet 5 | $0.00004 | $0.00699 |
| Haiku 4.5 | $0.00002 | $0.00349 |
Grade A, and why
pixel-definitions 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pixel Registry Definitions
Overview
Pixel definitions are JSON5 files that document pixels and wide events fired by the iOS and macOS apps. They live in:
- iOS:
iOS/PixelDefinitions/pixels/definitions/*.json5 - macOS:
macOS/PixelDefinitions/pixels/definitions/*.json5 - iOS wide events:
iOS/PixelDefinitions/wide_events/definitions/*.json5
Each platform has its own params_dictionary.json5 and suffixes_dictionary.json5 for reusable definitions.
Note: Each definitions directory contains a TEMPLATE.json5 file. These are scaffolds for creating new definition files — they are not real pixel definitions. Ignore them when reviewing or auditing existing definitions (their placeholder expires dates are intentional examples).
Pixel Definition Structure
Each .json5 file is a JSON5 object where keys are pixel names and values describe the pixel:
{
"pixel_name_here": {
"description": "When and why this pixel fires",
"owners": ["githubUsername"],
"triggers": ["other"],
"suffixes": ["first_daily_count", "platform", "form_factor"],
"parameters": ["appVersion", "errorCode", "errorDomain"],
// Only for temporary pixels — omit for permanent ones
"expires": "2025-06-30"
}
}
Required Fields
| Field | Type | Description |
|---|---|---|
description |
string | When the pixel fires and its purpose |
owners |
string[] | GitHub usernames of responsible people |
triggers |
string[] | What causes the pixel to fire (see trigger values below) |
Optional Fields
| Field | Type | Description |
|---|---|---|
suffixes |
array | Dynamic parts appended to the pixel name |
parameters |
array | Query parameters sent with the pixel |
expires |
string | ISO date (YYYY-MM-DD) for temporary pixels |
Trigger Values
Valid trigger values: "other", "scheduled", "startup", "page_load", "new_tab", "exception", "user_submitted", "search_ddg".
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 · 306 lines · 22 tokens per session scan A 576ffc738018
pixel-definitions is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (252 stars, last pushed 2d ago), licensed Apache-2.0. It adds 22 tokens to every session and 3,493 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.