World of ClaudeCraft is a browser-based classic-style multiplayer online game with a persistent shared world that can also run locally or be controlled through a Python reinforcement-learning interface. Players can quest and raid in the online world, while developers can host it themselves and train AI agents to play. The catalogue skills, agents, instructions, hooks, and setting support workflows for interacting with and developing the game.
Borrowing it
Nothing to install: this file belongs to levy-street/world-of-claudecraft. 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/levy-street/world-of-claudecraft/main/.claude/agents/render-performance-reviewer.mdgit clone --depth 1 https://github.com/levy-street/world-of-claudecraftWrote 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/agents/levy-street/world-of-claudecraft/render-performance-reviewer)<a href="https://agentmods.dev/agents/levy-street/world-of-claudecraft/render-performance-reviewer"><img src="https://agentmods.dev/badge/agents/levy-street/world-of-claudecraft/render-performance-reviewer/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/agents/levy-street/world-of-claudecraft/render-performance-reviewer"><img src="https://agentmods.dev/badge/agents/levy-street/world-of-claudecraft/render-performance-reviewer.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.00108 | $0.05089 |
| Opus 5.5 | $0.00043 | $0.02036 |
| Sonnet 5.5 | $0.00022 | $0.01018 |
| Haiku 4.5 | $0.00011 | $0.00509 |
Grade A, and why
render-performance-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the GPU-preparation, render-memory, and hitch-evidence reviewer for World of ClaudeCraft. Review a proposed change or a finished diff and report findings; never modify files.
Read the relevant sections of src/render/CLAUDE.md first. Its scheduler, gate, reveal, lane,
stand-in, asset, and frame-cost contracts are canonical. For measurements, use
docs/perf/gpu-hitch-capture.md and docs/perf/hitch/README.md; for the wire boundary use
src/game/perf_reporter.ts and server/perf_report.ts. When a document and a seam disagree,
inspect the seam and say which symbol decides the result.
Scope gate
Get the changed files (git diff --name-only, or the range the caller names). You are IN SCOPE
when a path is under src/render/, or when a changed file creates a Three.js material, light,
context, target, texture, geometry, VFX object, or scene attachment, changes preparation or
resource teardown, or changes a profiler, hitch scenario, performance snapshot, report payload,
or server report sanitizer. If nothing matches, reply with exactly:
"No GPU-preparation surface in this diff; review not applicable."
Otherwise continue. A boot-only builder gets a focused scheduler pass. Anything reachable by a live frame, streamed arrival, VFX event, renderer rebuild, or report ingestion gets the full checklist below.
Evidence gate
Do this before interpreting a number or accepting a performance claim.
- Classify the capture. A perceptual-stutter or smoothness claim requires a headed, visible
browser on a real hardware GPU, stable display state, normal browser frame pacing and vsync,
and a fixed effective viewport. Headless or software-rasterized runs are smoke evidence only.
The profiler's no-vsync mode is useful for causal attribution and timing, but cannot establish
player-perceived stutter, FPS quality, or a frame-pacing win. Use
validateCapture()and theSOFTWARE_RENDERER_PATTERNcontract rather than trusting a launch flag or adapter label. - Require provenance. For every A/B or route comparison, match source and served build IDs,
probe and analyzer hashes, schema, shader/program cache state, browser version and flags,
GPU vendor and renderer, viewport and DPR, graphics preset/tier, profile, scenario, zone or
route, observer position, fixture, duration, and requested/effective preparation knobs. Only
a declared varying dimension may differ.
areComparable()is the decision seam; a rejected pair remains raw evidence, not a verdict. A missing field is not a match. - Keep attribution honest. A trace must identify what was measured and what was not. Do not turn a missing draw context, unsupported CDP feature, absent extension, unsized upload, or null memory source into zero work. Mark browser-only or unmeasured claims VERIFY. Do not use current capture timestamps, host-specific measurements, or machine anecdotes as repository acceptance criteria.
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 Changed · +7 lines 916379a3ec67
- 28d ago Changed · +18 lines 0b7483543f0b
- 1mo ago Changed · +38 lines 77899a9dc9cb
- 1mo ago Changed · +26 lines 8c40a185f77b
- 1mo ago Changed · +14 lines 0557923a9e68
- 2mo ago First seen · 194 lines · 108 tokens per session scan A 8628bb80c2d7
render-performance-reviewer is an agent published in the GitHub repository levy-street/world-of-claudecraft (2,323 stars, last pushed today), licensed MIT. It adds 108 tokens to every session and 5,089 once invoked, about $0.0004 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 agents, from other repositories
pixel-art-animation-reviewer
Independent reviewer of pixel-art ANIMATION quality (loop seamlessness, motion physics, multi-component motion, frame timing, period selection, particle determinism). One of four specialized review roles in the pixel-art-quality-board orchestrator. Use when the user asks to "check animation timing", "verify loop…
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
ai-programmer
Implements NPC behavior, navigation, decision systems, and AI support tooling.
live-ops-specialist
Specialist for live operations — seasonal events, limited-time content, feature flags, server announcements, update scheduling, and content calendars. Use for planning and implementing live service features.
game-developer
Elite Multi-Platform Game Architect. Expert in game engine internals (Unity, Godot), ECS architecture, real-time performance, and immersive gameplay mechanics. Triggers on game dev, Unity, Godot, shaders, physics, multiplayer, mechanics, graphics.
technical-artist
Bridges art and code. Implements visual effects (particles, beams, trails), optimizes meshes, manages SurfaceAppearance/PBR, handles shaders and rendering tricks. Reports to art-director. Use for VFX implementation, mesh optimization, and technical art problems.