gpu-memory-and-batching SKILL.md skillA
gpu-memory-and-batching from yuiseki/map-from-scratch is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yuiseki/map-from-scratch/gpu-memory-and-batching@git:20261027.231c915Pins git:20261027.231c915 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yuiseki/map-from-scratch
- Path
.agents/skills/gpu-memory-and-batching/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261027.231c915, committed Oct 27, 2026
- First version recorded
- Oct 26, 2026
- Size
- 36,571 bytes
- Repository stars
- 24
- License
- GPL-3.0
How map engines cut draw calls, vertex bytes, uploads and GPU memory, which pools and caches they had to cap or remove, and what they reverted, distilled for a map-from-scratch renderer. Load it when designing the vertex layout or index format a bake writes, deciding how many draw calls a layer or tile becomes (batching, instancing, multi-draw), putting per-feature state on the GPU (attributes, uniforms, lookup textures), writing a buffer, texture or render-target pool, adding a…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# GPU memory and batching: few draws, few bytes, bounded pools A GPU renderer spends its frame on three things that a general engine multiplies by its generality: draw calls (and the state changes between them), bytes moved to the GPU (vertex layout, uploads, re-uploads), and GPU or heap memory held at once (buffers, textures, render targets, CPU copies of all of them). The engines in `ref-repos/` cited below have spent releases on these: merging per-feature meshes into batches, shrinking vertex formats, freeing CPU copies after upload, capping pools that grew without bound, and reverting caches that cost more memory than they saved. A map-from-scratch renderer starts from the place they converged on: the bake writes exactly the GPU layout, the renderer uploads it once and changes uniforms per frame [1]. This skill is for the decisions inside that rule, and for the moment the rule stops being enough (streamed tiles, run-time edits, a phone with 3 GB). Per-engine detail is in [references/engines.md](references/engines.md). Neighbouring skills: byte budgets for tile caches and fetch queues are in `tile-cache-and-loading`, glyph atlases and SDF text in …
Read the whole file at its exact version.
How to install
mdr add yuiseki/map-from-scratch/gpu-memory-and-batching@sha256:1f22b5f49fb31940The line at the top of this page pins the label git:20261027.231c915, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_v22visxcqqjhu6vq)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 26, 2026 and Oct 27, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.231c915 latest | 2026-10-27 | 231c915 | 36,571 B | A | view · diff |
| git:20261026.79a684e | 2026-10-26 | 79a684e | 36,566 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (36571 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
yuiseki/map-from-scratch · 24 stars · license GPL-3.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_v22visxcqqjhu6vq GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/map-from-scratch/gpu-memory-and-batching GET https://markdownregistry.com/api/v1/blob/1f22b5f49fb3194036ef1011fbaabb62dd7581d7af85802f6ee5f0824ac70fbf
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.