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/first-fluke/fullstack-starterWrote 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/first-fluke/fullstack-starter/i18n-arb)<a href="https://agentmods.dev/rules/first-fluke/fullstack-starter/i18n-arb"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/i18n-arb/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/first-fluke/fullstack-starter/i18n-arb"><img src="https://agentmods.dev/badge/rules/first-fluke/fullstack-starter/i18n-arb.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.00000 | $0.00370 |
| Opus 5.5 | $0.00000 | $0.00148 |
| Sonnet 5.5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
i18n-arb 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
ARB-Based Localization
When ARB files exist in the project, they are the single source of truth for all user-facing strings — regardless of target platform. A build step generates the platform-specific artifacts from ARB (e.g. JSON for web, generated Dart for Flutter).
- Never hardcode UI strings — all user-visible text must come from ARB files (
*.arb) - Edit ARB first — when adding or changing UI text, update the ARB file, then run the i18n build
- Build after changes — run the project's i18n build task (e.g.
mise i18n:build, ordart run build_runner buildin a Flutter package) to regenerate localized output (JSON for web, generated Dart, etc.). Prefer themisetask when one exists. - Generated output is never hand-edited — change the ARB and rebuild; treat the emitted JSON/Dart as derived artifacts
- Base locale — the primary ARB file (e.g.,
app_en.arb) is the reference; other locales derive from it - Key naming — use
camelCasekeys describing the purpose, not the content:loginButtonnotclickHere - Placeholders — use ICU message syntax for interpolation:
"greeting": "Hello, {name}!" - Do not translate keys — ARB keys are identifiers, always in English
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 · 21 lines · 0 tokens per session scan A b6b85b4c4b2c
i18n-arb is a cursor rule published in the GitHub repository first-fluke/fullstack-starter (224 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 370 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-09-03.
Other cursor rules, from other repositories
schemas
Sanity schema and Studio config conventions.
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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.