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 skills add andrewsrigom/agent-skills --skill next-intl-messages-and-formattinggit clone --depth 1 https://github.com/andrewsrigom/agent-skillsWrote 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/skills/andrewsrigom/agent-skills/next-intl-messages-and-formatting)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/next-intl-messages-and-formatting"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-messages-and-formatting/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/skills/andrewsrigom/agent-skills/next-intl-messages-and-formatting"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-messages-and-formatting.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.00071 | $0.00790 |
| Opus 5 | $0.00036 | $0.00395 |
| Sonnet 5 | $0.00014 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
next-intl-messages-and-formatting 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 12d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Intl Messages and Formatting
Use this skill when the task is about message authoring, translation consumption, or locale-aware formatting behavior.
Scope
- message catalog structure and namespace strategy
- ICU authoring patterns
useTranslations,t.rich,t.markup,t.raw,t.hasuseFormatterand named formats- typed ICU arguments and message validation
useExtractedas an optional workflow
Routing cues
- message JSON structure, namespace design, ICU, rich text, formatting, validation -> use this skill
defineRouting, locale switchers, domains, pathnames -> usenext-intl-routing-and-navigationgetTranslationsin metadata,setRequestLocale, testing, error files -> usenext-intl-server-runtime- plugin flags, TypeScript augmentation, Crowdin, loading strategy -> use
next-intl-workflows-and-tooling
Default path
- Read references/icu-rich-text-and-catalogs.md first.
- If the task touches formats, validation, or extracted messages, read references/formatting-validation-and-types.md.
- Keep namespaces close to the component boundary and choose the lowest stable common branch.
- Move language logic into ICU messages instead of branching in application code.
When to deviate
- Use server-side translation APIs only for the documented server exceptions.
- Reach for
t.markuponly when the output must stay string-based rather than React-node based. - Treat
useExtractedas opt-in workflow tooling, not the baseline message authoring model.
Guardrails
- Keep catalogs as nested objects. Do not use
.inside message keys. - Prefer consuming translations from components. Use server awaitables only for the official server-side exceptions.
- Do not call
useTranslationsoruseFormatterinasynccomponents. - Use
t.rich(...)for translatable markup. Avoid surrounding sentence fragments with hardcoded JSX. - Use
t.markup(...)when tags should compile to strings, not React nodes. - Use
format.list(...)for locale-aware lists instead of joining strings manually. - Treat
useExtractedas experimental, not as the default baseline.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 82 lines · 71 tokens per session scan A c3043a7b0467
next-intl-messages-and-formatting is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 790 once invoked, about $0.0004 per session on Opus 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-31.
Other skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.