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.
git clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/rules/perniemann/pncore/pn-three-game)<a href="https://agentmods.dev/rules/perniemann/pncore/pn-three-game"><img src="https://agentmods.dev/badge/rules/perniemann/pncore/pn-three-game.svg" alt="Measured on agentmods" 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.00374 | $0.00374 |
| Opus 5 | $0.00187 | $0.00187 |
| Sonnet 5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
pn-three-game 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.
What it actually says
Three.js / 2D game rules
- Prefer a clear scene hierarchy and naming (e.g. groups for logical parts) so objects can be found and disposed correctly.
- Dispose of geometries, materials, and textures when no longer needed to avoid memory leaks.
- For postprocessing: keep pass order explicit and document (e.g. comment or constant) so changes don't break expected visual order.
- In 2D game code: keep game logic (state, rules, scoring) separate from render/input where possible for testability and clarity.
- Avoid unnecessary draw calls and heavy per-frame allocations; reuse objects and buffers where it helps performance.
- R3F/Drei patterns: When using React Three Fiber, use
useLoader(cached) instead of manual loaders; use<Suspense>for async assets; keep scene graph components pure and side-effect-free. - Rapier physics: Set fixed timestep via
<Physics timeStep="vary">for determinism; pairRigidBodywith a matching collider; clean up withuseEffectreturn in R3F. - WebGPU/TSL (Three.js r167+): Use
WebGPURendererwith TSL node materials when targeting WebGPU; provide a WebGL fallback viaWebGLRendererfor unsupported browsers.
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 First seen · 17 lines · 374 tokens per session scan A 01ce0a79ea14
pn-three-game is a cursor rule published in the GitHub repository perniemann/pnCore (0 stars, last pushed today), licensed MIT. It adds 374 tokens to every session, about $0.0019 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-03.
Other cursor rules, from other repositories
t-800-mandatory-routing
A mandatory routing rule for creating or changing subagents, skills, commands, rules, and hooks. Hooks are scripts that run automatically when certain events occur.
t-800-operator-routing
A routing rule for explaining Cursor and its agent features to Russian-speaking beginners. Cursor is a code editor with built-in AI assistance.
t-800-factory-routing
A routing rule for building and coordinating groups of coding subagents. Subagents are separate agents that handle parts of a larger task.
t-800-cloud-hub-routing
A routing rule for Cloud Hub setup work, sending matching requests to a designated lead agent. Cloud Hub is the project area named in the rule.
typescript-conventions
Cursor rule "typescript-conventions" from VirtusLab-Open-Source/strapi-plugin-mcp, covering typescript and coding conventions, typescript configuration, import/export patterns, code organization and services (server/src/services/).
game-architect
Game Architect agent (Cloud Dragonborn).