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/gracefullight/docusaurus-pluginsWrote 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/gracefullight/docusaurus-plugins/i18n-guide)<a href="https://agentmods.dev/rules/gracefullight/docusaurus-plugins/i18n-guide"><img src="https://agentmods.dev/badge/rules/gracefullight/docusaurus-plugins/i18n-guide/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/gracefullight/docusaurus-plugins/i18n-guide"><img src="https://agentmods.dev/badge/rules/gracefullight/docusaurus-plugins/i18n-guide.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.01041 | $0.01041 |
| Opus 5.5 | $0.00416 | $0.00416 |
| Sonnet 5.5 | $0.00208 | $0.00208 |
| Haiku 4.5 | $0.00104 | $0.00104 |
Grade A, and why
i18n-guide 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.
How it starts
The opening of the file, as written. The whole thing — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i18n Guide — Response Language Rules
Rules for determining and applying response language across agents and workflows.
Language Resolution
Response language is determined by the following priority:
- User prompt language — if the user writes in a specific language, respond in that language
oma-config.yaml—languagefield in.agents/oma-config.yaml- Fallback — English (en) if neither of the above is set
# .agents/oma-config.yaml
language: ko # ko, en, ja, zh, ...
Translation Voice
When translating user-facing content, the translation_voice field in .agents/oma-config.yaml controls global rhythm and formality. It is applied on top of oma-translator content-type persona routing.
| Value | Effect |
|---|---|
formal |
strict complete sentences, no fragments, formal register only |
balanced (default) |
content-type defaults — fragments only in label/cell positions |
interpreter |
punchy, audience-first, spoken cadence; fragments allowed when natural |
Workflows that translate user-facing content should respect this setting via the oma-translator skill rather than hardcoding a tone.
What to Localize
| Category | Localize? | Example |
|---|---|---|
| Natural language responses | Yes | User-facing explanations and descriptions |
| Error messages (user-facing) | Yes | Authentication failure messages |
| Status updates / progress reports | Yes | "Phase 2 complete, starting Phase 3" |
| Charter Preflight output | Yes | Descriptive text localized, keywords stay in English |
| Result files (result-*.md) | Yes | User-readable text |
What Stays in English
| Category | Why | Example |
|---|---|---|
| Code (variables, functions, classes) | Codebase consistency | getUserProfile() |
| Git commit messages | Conventional commits standard | feat: add user auth |
| PR titles/body | GitHub collaboration standard | fix: resolve race condition |
| Technical / domain terms | Meaning loss when translated | API, JWT, middleware, scaffold |
| File paths / config keys | System identifiers | .agents/config/ |
| Log levels / status keywords | Parsing compatibility | Status: completed, BLOCKED |
| CLAUDE.md / SKILL.md content | System prompts | Keep English originals |
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 · 96 lines · 1,041 tokens per session scan A 3a16b7aad89c
i18n-guide is a cursor rule published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 24d ago), licensed MIT. It adds 1,041 tokens to every session, about $0.0042 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-09-03.
Other cursor rules, from other repositories
internationalization
A set of rules for internationalization, the practice of adapting an application for multiple languages and regions. It covers file structure, translation namespaces, and using translations in components.
cmd-moodle-mustache-lint
Lint Mustache templates for accessibility, security, hard-coded strings, and Moodle template conventions. (invoke by typing: @moodle-mustache-lint).
uninettuno-monografia
Regole UNINETTUNO per tesi TRIENNALE in italiano, con termini tecnici inglesi ammessi.
controlflow-docs-evals
Rules for documentation parity, localized tutorials, and eval verification.
report
A set of rules for generating HTML dashboards that present data and analysis in Korean. It defines the required page structure, visual libraries, fonts, and report content.
frontend-translation-management
Maintain consistent translation practices across the frontend application to ensure proper internationalization and user experience.