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/fuzzinggit 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/fuzzing)<a href="https://agentmods.dev/rules/quinnjr/skia-rs/fuzzing"><img src="https://agentmods.dev/badge/rules/quinnjr/skia-rs/fuzzing.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.00412 |
| Opus 5 | $0.00000 | $0.00206 |
| Sonnet 5 | $0.00000 | $0.00082 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
fuzzing 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
Fuzzing
Setup
# Install nightly toolchain and cargo-fuzz
rustup install nightly
cargo install cargo-fuzz
Running Fuzz Tests
# Run a fuzz target
cd fuzz
cargo +nightly fuzz run fuzz_point
# Run with time limit
cargo +nightly fuzz run fuzz_matrix -- -max_total_time=60
# List all targets
cargo +nightly fuzz list
Available Fuzz Targets
fuzz_point- Point operationsfuzz_rect- Rectangle operationsfuzz_matrix- Matrix transformationsfuzz_color- Color conversionsfuzz_path- Path constructionfuzz_path_builder- PathBuilder shapesfuzz_paint- Paint configurationfuzz_canvas- Canvas operations
Writing Fuzz Targets
#![no_main]
use arbitrary::Arbitrary;
use libfuzzer_sys::fuzz_target;
#[derive(Debug, Arbitrary)]
struct MyInput {
value: f32,
flag: bool,
}
fuzz_target!(|input: MyInput| {
// Skip invalid inputs early
if !input.value.is_finite() {
return;
}
// Test code that should not panic
let result = my_function(input.value);
// Assert invariants
assert!(result.is_valid());
});
Best Practices
- Use
Arbitraryderive for structured input - Validate and skip invalid inputs early
- Limit resource usage (iteration counts, sizes)
- Assert invariants, not expected failures
- Keep fuzz targets focused on specific functionality
- The
fuzzcrate usesedition = "2021"due tolibfuzzer-sysrequirements
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 · 78 lines · 0 tokens per session scan A ea8561eddd48
fuzzing 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 412 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.