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/core)<a href="https://agentmods.dev/rules/andvolodko/html5-game-editor/core"><img src="https://agentmods.dev/badge/rules/andvolodko/html5-game-editor/core/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/core"><img src="https://agentmods.dev/badge/rules/andvolodko/html5-game-editor/core.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.00258 | $0.00258 |
| Opus 5.5 | $0.00103 | $0.00103 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
core 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
Core invariants
Consult PROJECT.md for repository orientation when needed. For architectural or cross-package changes, consult the relevant documentation linked from PROJECT.md. Do not load unrelated documentation for localized changes.
- Runtime packages must not depend on editor packages. Games must ship without editor code.
- Serialized scene/domain data must stay serializable, deterministic, Git-friendly, and renderer-independent.
- Never persist
PIXI.*orTHREE.*runtime instances in scene/domain models. - Persisted asset references must use stable
assetIdvalues, not filesystem paths. - Browser filesystem access must go through project-server. Constrain paths to the active project root.
- Preserve package dependency direction. Domain packages must not import apps or editor UI. Avoid cycles.
- User-visible editor mutations should go through commands so undo/redo works. One completed gesture = one command.
- React is a view layer. It must not be the source of truth for scene/domain state.
- Reuse existing architecture before introducing new abstractions. Do not make unrelated changes.
- After implementation, run the relevant tests and typecheck for affected packages.
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 · 20 lines · 258 tokens per session scan A 070ad468a394
core is a cursor rule published in the GitHub repository andvolodko/html5-game-editor (12 stars, last pushed 11d ago), licensed MIT. It adds 258 tokens to every session, about $0.0010 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.