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/thematters/matters-webWrote 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/thematters/matters-web/internationalization)<a href="https://agentmods.dev/rules/thematters/matters-web/internationalization"><img src="https://agentmods.dev/badge/rules/thematters/matters-web/internationalization/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/thematters/matters-web/internationalization"><img src="https://agentmods.dev/badge/rules/thematters/matters-web/internationalization.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.00023 | $0.00581 |
| Opus 5.5 | $0.00009 | $0.00232 |
| Sonnet 5.5 | $0.00005 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
internationalization 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Internationalization (i18n)
Matters Web uses react-intl (FormatJS) for internationalization.
i18n Structure
lang/: Contains language filescompiled-lang/: Contains compiled language files used at runtime- Language strings are extracted from components and pages using formatjs
Translation Management
- The application uses a set of scripts to manage translations:
npm run i18n:extract: Extracts messages from the codebase tolang/npm run i18n:generate: Normalize language files tolang/npm run i18n:compile: Compiles language files tocompiled-lang/for use in the applicationnpm run i18n: Runs all i18n commands
Usage in Components
Components use the FormattedMessage component or the useIntl hook to access translations:
// Using FormattedMessage
<FormattedMessage
defaultMessage="Archived"
id="a/YQ1Z"
description="src/components/ArticleDigest/DropdownActions/ArchiveArticle/Dialog.tsx"
/>
// Using useIntl
const intl = useIntl()
const message = intl.formatMessage({
defaultMessage: 'Archived'
id="a/YQ1Z"
description="src/components/ArticleDigest/DropdownActions/ArchiveArticle/Dialog.tsx"
})
The id is an automatically generated hash that uniquely identifies each translatable message. The description field contains the relative path of the component file, which helps prevent ID collisions when the same defaultMessage appears in multiple components. This enables accurate message tracking and context-specific translations throughout the application.
Translation Workflow
- Add copy with
<FormattedMessage>orintl.formatMessagein your component - Run
npm run i18nto generate language files - Add corresponding translations to
lang/zh-Hans.jsonandlang/zh-Hant.json - Run
npm run i18nto compile the language files
Language Files
The main language files:
- lang/default.json: Default language strings
- lang/en.json: English translations
- lang/zh-Hant.json: Traditional Chinese translations
- lang/zh-Hans.json: Simplified Chinese translations
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 · 66 lines · 23 tokens per session scan A 2a0ad7139332
internationalization is a cursor rule published in the GitHub repository thematters/matters-web (86 stars, last pushed 5d ago), licensed Apache-2.0. It adds 23 tokens to every session and 581 once invoked, about $0.0001 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-30.
Other cursor rules, from other repositories
app-router-setup
Getting started with your Sitecore Content SDK Next.js App Router project.
i18n-and-generated-code
Paraglide i18n for all user-facing strings, and rules for generated code.
i18n-mandatory
All user-visible UI text uses t('namespace:section.key') from react-i18next.
i18n
Internationalization with react-i18next.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.