vgpu is a TypeScript library that provides one WebGPU programming interface for browser rendering, headless Node execution, and deterministic tests, including shader modules, 3D scenes, GPU tensors, neural networks, and mathematical visualizations. Developers use it to write explicit GPU drawing and computation code while sharing it across runtimes without hidden global state. The catalogue skill supports work with this library.
Borrowing it
Nothing to install: this file belongs to vercel-labs/vgpu. 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/vercel-labs/vgpu/canary/AGENTS.mdgit clone --depth 1 https://github.com/vercel-labs/vgpuWrote 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/instructions/vercel-labs/vgpu/agents-md)<a href="https://agentmods.dev/instructions/vercel-labs/vgpu/agents-md"><img src="https://agentmods.dev/badge/instructions/vercel-labs/vgpu/agents-md/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/instructions/vercel-labs/vgpu/agents-md"><img src="https://agentmods.dev/badge/instructions/vercel-labs/vgpu/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.01035 | $0.01035 |
| Opus 5 | $0.00517 | $0.00517 |
| Sonnet 5 | $0.00207 | $0.00207 |
| Haiku 4.5 | $0.00103 | $0.00103 |
Grade A, and why
vgpu AGENTS.md 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 yesterday.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working on vgpu
Normal development targets canary. Read CONTRIBUTING.md before preparing a PR or release.
Every PR declares its type
Include exactly one ## PR type section with exactly development or release, never a default
or inference from the title/branch. release prepares a new RC/stable package version on canary;
all other work uses development, including promotions to main (governed by main-policy) and
synchronization of versions already accounted for on the target branch. This is independent of impact:
a release-preparation PR normally declares impact none.
The trusted release-impact check validates this decision on commits AND description edits. New public
package version changes on canary cannot be labeled development. A release PR must advance the
current canary version, have coherent public package versions, include a substantive ## Migration review
section and pass the same strict migration readiness check used at publication. Finalize the guide
before opening the release PR; do not wait for publishing CI to discover an unfinished review.
Every PR declares release impact
Include exactly one ## Release impact section in the PR description:
none — <specific reason consumers are unaffected>for tests, CI, repository/site docs with no published-package effect, release preparation, behavior-preserving internal refactors, or promotion/synchronization of changes already accounted for in their original PRs.changeset — .changeset/<id>.mdfor changes to published behavior. List multiple new changesets with commas.
Use a meaningful filename, not the placeholders above. The release-impact check runs again when
the PR description changes. Review the declaration against the diff: CI checks structure, not the
truth of a compatibility claim. Never declare none merely to satisfy a failing check.
Documentation bundled into the CLI/MCP corpus affects the published package and needs a changeset.
Write migration notes while changing code
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.
- yesterday First seen · 71 lines · 1,035 tokens per session scan A 834d6b907c03
vgpu AGENTS.md is an instructions file published in the GitHub repository vercel-labs/vgpu (2,016 stars, last pushed yesterday), licensed MIT. It adds 1,035 tokens to every session, about $0.0052 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-09-10.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).