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/network-quality-scoringgit 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/network-quality-scoring)<a href="https://agentmods.dev/rules/duckduckgo/apple-browsers/network-quality-scoring"><img src="https://agentmods.dev/badge/rules/duckduckgo/apple-browsers/network-quality-scoring.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.01547 |
| Opus 5 | $0.00000 | $0.00773 |
| Sonnet 5 | $0.00000 | $0.00309 |
| Haiku 4.5 | $0.00000 | $0.00155 |
Grade A, and why
network-quality-scoring 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 3d 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 — 180 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NetworkQualityMonitor Scoring Algorithm
Overview
NetworkQualityMonitor uses a browser-optimized scoring algorithm that prioritizes latency and consistency over raw bandwidth. The scoring is weighted as follows:
- HTTP Response (40%): Most critical for browser experience
- Bandwidth (35%): Important for media and downloads
- DNS (10%): Foundation of all connections
- Buffer Bloat (15%): Network congestion under load
HTTP Response Scoring (40% Weight)
Measurement Process
- Endpoints: Tests 10+ global endpoints including DuckDuckGo, major CDNs, and popular platforms
- Sampling: 15 requests per endpoint with interleaved ordering to avoid bias
- Statistical Analysis:
- Calculates median response time for each site
- Uses median of all site medians for overall response time
- Calculates standard deviation for each site's measurements
- Uses median of all site standard deviations for consistency metric
Response Time Calculation
// For each site: calculate median of its measurements
let siteMedians = sites.map { calculateMedian($0.measurements) }
// Overall response time: median of all site medians
let overallResponseTime = median(siteMedians)
This approach:
- Resists outliers at both per-site and cross-site levels
- Provides typical latency experience across geographic regions
- Doesn't get skewed by one particularly fast CDN or slow server
Consistency Calculation
// For each site: calculate standard deviation of its measurements
let siteStdDevs = sites.map { calculateStdDev($0.measurements) }
// Overall consistency: median of all site standard deviations
let overallStdDev = median(siteStdDevs)
This avoids mixing different latency populations (e.g., 20ms CDN vs 300ms cross-ocean).
Coefficient of Variation (CV) Scoring
The scoring uses Coefficient of Variation to fairly compare different latency ranges:
// CV = stdDev / mean - normalizes variance relative to baseline
let coefficientOfVariation = stdDev / averageResponseTime
// Apply CV-based penalty (fairer than raw standard deviation)
// Example: 10ms variance on 50ms latency (20% CV) penalized more than
// 10ms variance on 200ms latency (5% CV)
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.
- 3d ago First seen · 180 lines · 0 tokens per session scan A a2e0795781ae
network-quality-scoring is a cursor rule published in the GitHub repository duckduckgo/apple-browsers (251 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,547 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
vasu-playwright-utils
../../templates/cursor-rules/vasu-playwright-utils.mdc.
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.