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/no-magic-numbersgit 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/no-magic-numbers)<a href="https://agentmods.dev/rules/andvolodko/html5-game-editor/no-magic-numbers"><img src="https://agentmods.dev/badge/rules/andvolodko/html5-game-editor/no-magic-numbers.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.00000 | $0.00362 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
no-magic-numbers 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 6d 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
No magic numbers
Do not leave unexplained numeric literals in behavior code. Name values that encode domain meaning, UI layout, input protocols, timing, or rendering.
Prefer
const MIDDLE_MOUSE_BUTTON = 1;
const VIEWPORT_SCALE_STEP = 0.1;
const DEFAULT_FONT_SIZE = 24;
if (event.button === MIDDLE_MOUSE_BUTTON) { /* … */ }
Colocate constants with the module that owns them, or share via a small *-constants.ts / existing domain module when reused across files.
Allowed without naming
- Loop / array indices and obvious arithmetic (
i + 1,length - 1,/ 2for midpoint). - Identity math (
* 1,+ 0) and empty defaults (0,1for scale/alpha when they are literal identities). - Enum-like discriminants already expressed as string unions or typed enums.
- Test expectations that mirror a fixture’s explicit setup values in the same test.
- CSS in stylesheets / style objects when the number is a one-off layout token next to related styles (prefer design tokens when the value repeats).
Do not
- Scatter the same literal (e.g.
0.1,24, button1) across files — extract one shared constant. - Name every trivial
0/1; name values a reader would otherwise have to reverse-engineer. - Put renderer/UI literals into serialized scene defaults unless they are real domain defaults (then name them in the domain/factory module).
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.
- 6d ago First seen · 36 lines · 0 tokens per session scan A ce9cbba8e916
no-magic-numbers is a cursor rule published in the GitHub repository andvolodko/html5-game-editor (6 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 362 tokens. 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
nextjs-typescript-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with TypeScript and Tailwind CSS integration.
nextjs-tailwind-typescript-apps-cursorrules-prompt
Cursor rules for Next.js development with Tailwind CSS and TypeScript integration.
qwik-tailwind-cursorrules-prompt-file
Cursor rules for Qwik development with Tailwind CSS integration.
ts-coding-rules
The current codebase enforces strict type safety, accessibility standards, and consistent code quality for JavaScript/TypeScript projects using Biome's lightning-fast formatter and linter.
svelte-typescript
Svelte 5 and TypeScript patterns for Keymoji components and stores.
ultracite
Ultracite Rules - AI-Ready Formatter and Linter.