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/development-commandsgit clone --depth 1 https://github.com/duckduckgo/apple-browsersWhat 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.01560 | $0.01560 |
| Opus 5 | $0.00780 | $0.00780 |
| Sonnet 5 | $0.00312 | $0.00312 |
| Haiku 4.5 | $0.00156 | $0.00156 |
Grade A, and why
development-commands 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Development Commands & Build Instructions
📋 When to Use This Document
Use these instructions when you need to:
- Build the iOS Browser app for testing or development
- Build the macOS Browser app for testing or development
- Verify that code changes compile successfully
- Prepare the app for testing or debugging
- Understand build failures and how to fix them
🚦 Golden Rules for Building
✅ ALWAYS DO THESE
- Use the full shell wrapper:
/bin/sh -c 'set -e -o pipefail && xcodebuild ... | xcbeautify' - Detect environment first: Never hardcode paths or simulator IDs
- Check exit codes: Ensure the build succeeded before proceeding
- Use absolute paths: Always use full paths for workspace files
- Include xcbeautify: Output is unreadable without it
❌ NEVER DO THESE
- Never use
-jobsflag: It's been removed from all commands - Never skip xcbeautify: Raw xcodebuild output is nearly impossible to parse
- Never use .xcodeproj files: Always use .xcworkspace
- Never hardcode simulator IDs: They change between systems
- Never ignore build failures: Always check and handle errors
🔍 Phase 1: Environment Detection
Pre-Flight Checks
Before building, validate your environment.
Example: See pre-flight-checks.sh
Required Variables to Detect
| Variable | Purpose | Detection Command | Expected Format |
|---|---|---|---|
WORKSPACE_PATH |
Full path to .xcworkspace | pwd + find . -name "DuckDuckGo.xcworkspace" |
/Users/.../DuckDuckGo.xcworkspace |
SIMULATOR_ID |
iOS Simulator UUID | xcrun simctl list devices | grep iPhone |
XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX |
ARCHITECTURE |
Mac CPU type | uname -m |
arm64 or x86_64 |
Detection Commands
Example: See environment-detection.sh
🏗️ Phase 2: Build Execution
iOS Build Command Template
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 First seen · 175 lines · 1,560 tokens per session scan A 661406c6b67c
development-commands is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (252 stars, last pushed today), licensed Apache-2.0. It adds 1,560 tokens to every session, about $0.0078 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.