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/quinnjr/skia-rs/benchmarkinggit clone --depth 1 https://github.com/quinnjr/skia-rsWrote 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/quinnjr/skia-rs/benchmarking)<a href="https://agentmods.dev/rules/quinnjr/skia-rs/benchmarking"><img src="https://agentmods.dev/badge/rules/quinnjr/skia-rs/benchmarking.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.00317 |
| Opus 5 | $0.00000 | $0.00159 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00032 |
Grade A, and why
benchmarking 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.
What it actually says
Benchmarking
Using the Benchmark System
# Run all benchmarks
cargo bench -p skia-rs-bench
# Run specific suite
cargo bench -p skia-rs-bench --bench core_benchmarks
# Quick validation
cargo bench -p skia-rs-bench -- --test
Writing Benchmarks
use criterion::{criterion_group, criterion_main, Criterion};
use std::hint::black_box;
fn bench_example(c: &mut Criterion) {
let mut group = c.benchmark_group("Example");
group.bench_function("operation", |b| {
b.iter(|| {
// Use black_box to prevent optimization
black_box(some_operation())
})
});
group.finish();
}
criterion_group!(benches, bench_example);
criterion_main!(benches);
Performance Targets
- Core operations (Point, Rect, Color): < 10ns
- Matrix operations: < 100ns
- Path operations: < 1µs per segment
- Canvas drawing: comparable to native Skia
Best Practices
- Use
std::hint::black_boxto prevent compiler optimizations - Use deterministic RNG for reproducible benchmarks
- Group related benchmarks together
- Include baseline comparisons where possible
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 · 58 lines · 0 tokens per session scan A adcdd179e2d4
benchmarking is a cursor rule published in the GitHub repository quinnjr/skia-rs (32 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 317 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
core
Core STT/TTS abstraction layer documentation.
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
arc-deref-pattern
When implementing parallel (Mt) algorithms in Verus, do NOT assume.
wrap-vs-specify
When to use externaltypespecification vs wrapper struct for Verus specs.