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-server-runtimegit 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-server-runtime)<a href="https://agentmods.dev/skills/andrewsrigom/agent-skills/next-intl-server-runtime"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-server-runtime/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-server-runtime"><img src="https://agentmods.dev/badge/skills/andrewsrigom/agent-skills/next-intl-server-runtime.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.00078 | $0.00952 |
| Opus 5 | $0.00039 | $0.00476 |
| Sonnet 5 | $0.00016 | $0.00190 |
| Haiku 4.5 | $0.00008 | $0.00095 |
Grade A, and why
next-intl-server-runtime 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 9d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next Intl Server Runtime
Use this skill when the task is about request-scoped config, server-side API selection, or rendering correctness across server and client boundaries.
Scope
i18n/request.ts,getRequestConfig, andrequestLocale- component environment rules for hooks vs awaitable APIs
NextIntlClientProviderinheritance, opt-out, and client wrapperssetRequestLocaleand static rendering- metadata, Server Actions, Route Handlers, sitemap, manifest, and OG images
- error files and testing translated components
Routing cues
getRequestConfig,requestLocale,NextIntlClientProvider,setRequestLocale, metadata, Server Actions, Route Handlers, sitemap, manifest, OG images, error files, tests -> use this skill- locale routing, domains, pathnames, locale switchers -> use
next-intl-routing-and-navigation - ICU authoring,
t.rich,useFormatter, message validation -> usenext-intl-messages-and-formatting - plugin flags, augmentation, Crowdin,
useExtracted-> usenext-intl-workflows-and-tooling
Default path
- Read references/environment-api-matrix.md first.
- If the task touches static rendering, error files, or tests, read references/static-rendering-errors-and-tests.md.
- Centralize request-scoped config in
i18n/request.ts. - Choose hook APIs only for non-async components. Choose awaitable server APIs everywhere else.
When to deviate
- Pass
localeexplicitly when the server surface does not infer it from the current segment. - Use client wrappers only when client-only provider props like
onErrororgetMessageFallbackare needed. - Move to routing skill when locale negotiation and URL structure dominate the task.
Guardrails
- Use hooks like
useTranslationsonly in non-async shared or client components. - Use
next-intl/serverawaitables inasynccomponents, metadata, Server Actions, and Route Handlers. - Await
requestLocaleand handle invalid,undefined, and explicit-override cases deliberately. - Return the resolved
localefromgetRequestConfig(...)explicitly. - Validate incoming locales before using them.
- Call
setRequestLocale(locale)before any next-intl API in every locale page or layout that must stay static. - Pass
localeexplicitly to awaitable APIs in metadata, manifest, sitemap, OG-image, and other non-component server surfaces when the locale is not inferred from the segment. NextIntlClientProviderinheritslocale,messages,formats,timeZone, andnow. Usemessages={null}to opt out, and a client wrapper foronErrororgetMessageFallback.- Provide
NextIntlClientProviderin tests and in client-only error surfaces.
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.
- 9d ago First seen · 88 lines · 78 tokens per session scan A 0edd6d57dcae
next-intl-server-runtime is a skill published in the GitHub repository andrewsrigom/agent-skills (2 stars, last pushed 5mo ago), licensed MIT. It adds 78 tokens to every session and 952 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.