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/ddebixx/frontend-template/i18ngit clone --depth 1 https://github.com/ddebixx/frontend-templateWhat 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.00000 | $0.00276 |
| Opus 5 | $0.00000 | $0.00138 |
| Sonnet 5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
i18n 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 2d 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
Copy & internationalization
No inline static display strings
Do not put user-visible (or a11y) string literals in components, pages, or features.
Move copy to either:
- Locale catalogs —
src/messages/*.jsonviat/getTranslations(multi-locale) - Constants —
*.constants.tsorsrc/constants/(keeps UI files clear)
The project chooses catalogs, constants, or a mix. Prefer catalogs when locales matter. Document a team default in the README if needed.
OK as literals: class names, URLs, analytics ids, enums, test fixtures.
Stack (templates)
- Next.js →
next-intl(src/i18n/request.ts+setLocalecookie) - Vite →
i18next+react-i18next(src/i18n/setup.ts) - Shared switcher:
components/shared/LocaleSwitcher - Stable keys;
Intl/library for dates, numbers, plurals; set documentlang
Details: docs/frontend/tools/I18N.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.
- 2d ago First seen · 30 lines · 0 tokens per session scan A c3324116785f
i18n is a cursor rule published in the GitHub repository ddebixx/frontend-template (3 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 276 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
internationalization
Cursor rule "internationalization" from dtyq/magic, covering internationalization (i18n) rules, 国际化基本规范, 1. 文件结构, 2. 命名空间规范 and 3. 组件中使用国际化.
i18n
USE WHEN: Managing translation files (JSON), localization keys, or implementing multi-language logic.
i18n-translation-system
This project implements an intelligent translation system with incremental detection and language validation.
mf-expo-ship-checklist
When mf-expo work is finished — i18n, API usage, CHANGELOG.
controlflow-docs-evals
Rules for documentation parity, localized tutorials, and eval verification.
report
보고서를 작성할 때 참고하세요.