device-loss-and-limits

device-loss-and-limits is a cursor rule for Cursor from williammelin/webgpu-r3f-claude-skill. It costs 479 tokens per session, scanned A, original, no licence file.

Guidance for handling a lost WebGPU device and checking the limits and optional features supported by the user's graphics hardware. WebGPU is the browser API that lets web applications use the GPU.

In plain words
What is it for?
Use it to add recovery after GPU failures, request higher device limits, or enable optional features such as timestamp queries and float32 filtering.
Why use it?
It helps an application respond when the GPU connection fails and avoid requesting settings that a particular device does not support.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it to add recovery after GPU failures, request higher device limits, or enable optional features such as timestamp queries and float32 filtering.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits
Install

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.

Clone the repo
git clone --depth 1 https://github.com/williammelin/webgpu-r3f-claude-skill

Made for: Cursor.

Wrote 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.

agentmods badge for device-loss-and-limits

README.md
[![agentmods](https://agentmods.dev/badge/rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits/github.svg)](https://agentmods.dev/rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits)
Your own site
<a href="https://agentmods.dev/rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits"><img src="https://agentmods.dev/badge/rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits/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.

agentmods 80×15 button for device-loss-and-limits

Your own site · 80×15
<a href="https://agentmods.dev/rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits"><img src="https://agentmods.dev/badge/rules/williammelin/webgpu-r3f-claude-skill/device-loss-and-limits.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 479 This file is loaded in full into every session.
When invoked 479 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00479 $0.00479
Opus 5 $0.00239 $0.00239
Sonnet 5 $0.00096 $0.00096
Haiku 4.5 $0.00048 $0.00048

Measured 8d ago against content hash 3da3b08a17e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

device-loss-and-limits 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 8d 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.

.cursor/rules/device-loss-and-limits.mdc · 42 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 8d ago First seen · 42 lines · 479 tokens per session scan A 3da3b08a17e3

Subscribe to this mod's changes

device-loss-and-limits is a cursor rule published in the GitHub repository williammelin/webgpu-r3f-claude-skill (2 stars, last pushed 6d ago), with no licence file. It adds 479 tokens to every session, about $0.0024 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-08-31.