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/andvolodko/html5-game-editorWrote 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/andvolodko/html5-game-editor/class-size)<a href="https://agentmods.dev/rules/andvolodko/html5-game-editor/class-size"><img src="https://agentmods.dev/badge/rules/andvolodko/html5-game-editor/class-size/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/rules/andvolodko/html5-game-editor/class-size"><img src="https://agentmods.dev/badge/rules/andvolodko/html5-game-editor/class-size.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.00036 | $0.00270 |
| Opus 5.5 | $0.00014 | $0.00108 |
| Sonnet 5.5 | $0.00007 | $0.00054 |
| Haiku 4.5 | $0.00004 | $0.00027 |
Grade A, and why
class-size 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 1mo 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
Class and module size
Prefer modules/classes under ~300 lines when they hold behavior. Treat ~500+ lines or 2+ unrelated responsibility clusters as a required split before adding more features there.
How to split
- Extract pure helpers / registries first (no behavior change).
- Extract collaboration objects (texture cache, drag controller) with clear ownership.
- Keep thin façades (
Editor,PixiSceneRenderer) that delegate.
React surfaces: extract hooks / row / menu components when a panel mixes tree + DnD + menus + rename.
Strategy registries (painters, factories, node-type defs, inspector fields): one visual category per file, not one mega-switch. Align splits across visual-components → schema → factories → pixi-definitions → painters → inspector fields.
Do not
- Split solely to hit a line count if the module is one coherent algorithm.
- Move domain logic into React, or renderer objects into serialized scene data.
- Create circular package deps while extracting.
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.
- 1mo ago First seen · 25 lines · 36 tokens per session scan A 3d62fdad33f8
class-size is a cursor rule published in the GitHub repository andvolodko/html5-game-editor (12 stars, last pushed 13d ago), licensed MIT. It adds 36 tokens to every session and 270 once invoked, about $0.0001 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-31.
Other cursor rules, from other repositories
javascript-typescript-code-quality-cursorrules-pro
Cursor rules for JavaScript and TypeScript development with code quality integration.
eslint
This guide defines the definitive ESLint configuration and best practices for our team, ensuring consistent code quality, early error detection, and seamless integration with modern JavaScript and TypeScript workflows.
general-code-quality-and-style
Project-wide rules for readable, maintainable TypeScript code, functional programming, file organization, naming, modular design, reviews, and web performance.
hatch3r-typescript-patterns
TypeScript and JavaScript typing mechanics — satisfies over as, discriminated unions, branded types, strict utility types, barrel exports, and import ordering.
api-design-typescript
API Design for TypeScript — Express, NestJS, Fastify patterns, middleware, validation, and error handling. Extends core/rules/api-design.mdc with TypeScript-specific guidance.
typescript
TypeScript best practices — strict configuration, advanced type patterns, type safety, generics, branded types, type guards, performance, testing, and common anti-patterns. Applied when working with TypeScript files.