Borrowing it
Nothing to install: this file belongs to gridaco/nothing. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/gridaco/nothing/main/.agents/skills/render-perf/SKILL.mdgit clone --depth 1 https://github.com/gridaco/nothingWrote 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/skills/gridaco/nothing/render-perf)<a href="https://agentmods.dev/skills/gridaco/nothing/render-perf"><img src="https://agentmods.dev/badge/skills/gridaco/nothing/render-perf/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/gridaco/nothing/render-perf"><img src="https://agentmods.dev/badge/skills/gridaco/nothing/render-perf.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 4 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 45 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 136 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 134 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium MCP Rug Pull · line 706 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.1 | $0.00055 | $0.07744 |
| Opus 5.5 | $0.00022 | $0.03098 |
| Sonnet 5.5 | $0.00011 | $0.01549 |
| Haiku 4.5 | $0.00006 | $0.00774 |
Grade A, and why
render-perf 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 2mo 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 — 724 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grida Canvas Engine — Performance Development
Workflow and reasoning framework for render performance work on the Grida Canvas Rust engine.
When to Use This Skill
- Benchmarking canvas rendering
- Optimizing frame time for any camera operation
- Designing or modifying caching strategies
- Analyzing benchmark results
- Writing or auditing benchmarks
- Investigating performance regressions
How to Orient Yourself
Before touching any code, build context by reading these sources in order:
- Read
crates/grida/AGENTS.md— crate conventions, test/check commands, benchmarking instructions. - Read
docs/wg/feat-2d/optimization.md— the master optimization document. It describes every optimization strategy, measured costs, and the rendering pipeline. This is the single most important file. - Browse
docs/wg/research/chromium/— research notes on how Chromium solves equivalent problems. Start withindex.mdfor the map, then read whichever documents match the problem at hand. - Read existing benchmarks — look in
crates/grida/benches/to understand what is already measured and how. - Read
crates/grida_dev/src/main.rs— thebenchandbench-reportsubcommands show how GPU benchmarks work with real.gridascene files.bench-reportis the bulk mode that outputs JSON across all fixtures.
Use grep and glob to discover the current state of code rather than
relying on hardcoded paths. File locations shift as the engine evolves.
Key discovery queries
| What you need | How to find it |
|---|---|
| The renderer entry point | grep "struct Renderer" --include="*.rs" in crates/grida/src/ |
| Camera change classification | grep "enum CameraChangeKind" --include="*.rs" |
| How compositor cache works | grep "struct LayerImage" --include="*.rs" and read the containing module |
| Promotion heuristics | grep "fn should_promote" --include="*.rs" |
| Where zoom invalidation happens | grep "zoom_changed|mark_all_stale|invalidate_all" --include="*.rs" in src/runtime/ |
| Frame pipeline flow | Search for fn queue|fn flush|fn draw|fn frame in the renderer file |
| Benchmark fixture scenes | --list-scenes flag on grida_dev bench, or run bench-report on a directory |
| Config toggles (compositing, atlas, etc.) | grep "set_layer_compositing|set_compositor_atlas|set_interaction_render_scale" --include="*.rs" |
Existing .plan.md proposals |
glob "docs/wg/feat-2d/*.plan.md" |
| Scene loading pipeline | grep "fn load_scene" --include="*.rs" in src/runtime/scene.rs |
| Layout engine entry point | grep "fn compute\b" --include="*.rs" in src/layout/engine.rs |
| Text measurement stats | grep "ParagraphMeasureStats" --include="*.rs" |
| Skip-layout config | grep "skip_layout" --include="*.rs" in src/runtime/ |
| Load-bench CLI tool | Read crates/grida_dev/src/bench/load_bench.rs |
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.
- 2mo ago First seen · 724 lines · 55 tokens per session scan A 8b9e907e33ee
render-perf is a skill published in the GitHub repository gridaco/nothing (54 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 55 tokens to every session and 7,744 once invoked, about $0.0002 per session on Opus 5.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-08-30.
Other skills, from other repositories
freya
Freya Rust GUI framework best practices, patterns, and conventions. Use when writing Freya components, hooks, elements, or working on a Freya project.
domain-fintech
A guide for building financial software in Rust, including systems that handle money, payments, trades, or accounting records. It covers currency values, precision, rounding, and exchange rates.
domain-fintech
A set of guidance for building financial software, such as trading, payment, currency, and accounting systems.
tigeropen-rust
A Rust SDK skill set for connecting applications to Tiger Brokers, an online brokerage, through its OpenAPI.
rust-patterns
Idiomatic Rust patterns, ownership, error handling, traits, concurrency, and best practices for building safe, performant applications.
money
Skill "money" from Hmbown/Codewhale, covering money, when to use, setup, workflow and non-goals.