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 instructions/duckduckgo/apple-browsers/agents-mdgit 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/instructions/duckduckgo/apple-browsers/agents-md)<a href="https://agentmods.dev/instructions/duckduckgo/apple-browsers/agents-md"><img src="https://agentmods.dev/badge/instructions/duckduckgo/apple-browsers/agents-md.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.00449 | $0.00449 |
| Opus 5 | $0.00225 | $0.00225 |
| Sonnet 5 | $0.00090 | $0.00090 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
apple-browsers AGENTS.md 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 today.
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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This file configures AI coding assistants for the Apple monorepo.
Development rules are maintained in .cursor/rules/ as the single source of truth.
Personal preferences (workflow, communication style, tool settings) belong in your tool's user-level config, not here:
- Claude Code:
~/.claude/CLAUDE.md - Cursor: User-level settings
This repo-level file is for team-shared conventions only.
Mandatory Rules
Detailed rules live in .cursor/rules/. Read from the list below when the request is relevant. Do not read any other files in .cursor/rules unless requested explicitly.
| File | Covers |
|---|---|
general.mdc |
Project overview, architecture summary, rule index, quick-start checklists |
code-style.mdc |
Full Swift style guide: naming, formatting, closures, optionals, memory management |
anti-patterns.mdc |
What NOT to do: singletons, async mistakes, SwiftUI pitfalls, testing mistakes |
user-defaults-storage.mdc |
Storing settings or preferences via KeyValueStore |
pixels.mdc |
Defining, naming, or firing pixel events |
project-structure.mdc |
Adding files or directories to the iOS project; buildable folders and Xcode groups |
Testing against the Privacy Configuration
Do not write unit tests that assert the current state of the Privacy Configuration, such as whether a particular feature or flag is present, absent, enabled, or disabled. The Privacy Configuration is controlled remotely, so tests that rely on it too strongly may be affected.
Instead, arrange each relevant configuration state explicitly and verify the app's behavior in that state. Where applicable, verify behavior when flags are added or removed, enabled or disabled, or changed while the app is running.
Opening a PR with snapshot changes
Before opening a monorepo PR, if the working tree has changes under the SnapshotReferences submodule, run ./scripts/open-snapshot-submodule-pr.sh first, then add the submodule PR link it prints to the monorepo PR description.
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.
- today Changed · +6 lines · +101 tokens per session 1f1cae9e9454
- 3d ago First seen · 27 lines · 348 tokens per session scan A 46989f204620
apple-browsers AGENTS.md is an instructions file published in the GitHub repository duckduckgo/apple-browsers (251 stars, last pushed today), licensed Apache-2.0. It adds 449 tokens to every session, about $0.0022 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 instructions, from other repositories
outline-apps AGENTS.md
AGENTS.md instructions for OutlineFoundation/outline-apps, covering welcome to the outline monorepo!, repository structure, the npm run action command, common actions and other useful commands.
FluidAudio CLAUDE.md
Claude Code instructions for FluidInference/FluidAudio, covering claude.md, project overview, critical development rules, never use @unchecked sendable and never create dummy models or synthetic data.
FluidAudio copilot-instructions.md
Copilot instructions for FluidInference/FluidAudio, covering fluidaudio - agent development guide, build & test commands, architecture, critical rules and code style (swift-format config).
outline-apps CLAUDE.md
Claude Code instructions for OutlineFoundation/outline-apps: This project uses AGENTS.md instead of CLAUDE.md.
speech-swift AGENTS.md
AGENTS.md instructions for soniqo/speech-swift, covering agent instructions, communication style, workflow, running tests and benchmarks — sequential and memory-aware and git conventions.
lotti AGENTS.md
AGENTS.md instructions for matthiasn/lotti, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.