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.
npx agentmods add rules/andvolodko/html5-game-editor/architecturegit 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/architecture)<a href="https://agentmods.dev/rules/andvolodko/html5-game-editor/architecture"><img src="https://agentmods.dev/badge/rules/andvolodko/html5-game-editor/architecture.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 | $0.00049 | $0.00388 |
| Opus 5 | $0.00024 | $0.00194 |
| Sonnet 5 | $0.00010 | $0.00078 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
architecture 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 4d 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
Architecture (on-demand)
Consult PROJECT.md for orientation. Read only the detailed docs that match this change. Do not load unrelated documentation for localized work.
For multi-package or schema/boundary changes, follow .cursor/skills/architecture-change/SKILL.md.
Constraints beyond .cursor/rules/core.mdc
- Prefer component composition over node-type inheritance (
Node+Transform2D+Sprite, notSpriteButtonNode extends SpriteNode). - Mutation path: UI → Command → domain model → renderer sync. Never React →
PIXI.*/THREE.*. - Persisted scene/project/asset formats must stay versioned; incompatible changes need migrations.
- Editable game content lives under
games/<name>/(not a top-levelprojects/tree).project-serverdefaults togames/editor-features-demo; override withPROJECT_ROOT. - Renderer-specific code belongs in
renderer-pixiorrenderer-three. Games that do not use Three.js must not be forced to bundle it. - Aseprite sources stay under
assets/; derived PNG/JSON under.generated/. Persist the sourceassetId(+ optional animation tag), never a generated path. Seedocs/assets.mdanddocs/aseprite.md.
Before coding an architectural change
- Inspect existing packages and public APIs.
- Identify undo/redo, persistence/schema, renderer, and test implications.
- Do not start until the plan is coherent.
Detailed docs: docs/architecture.md, plus the task-specific files listed in PROJECT.md.
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.
- 4d ago First seen · 28 lines · 49 tokens per session scan A a5b8af4a18a9
architecture is a cursor rule published in the GitHub repository andvolodko/html5-game-editor (6 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 388 once invoked, about $0.0002 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-08-31.
Other cursor rules, from other repositories
dev-browser
Fallback browser automation with persistent Chrome state. Use only when Browser Use is unavailable or blocked.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.