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 yildizberkay/skills --skill react-i18nextgit clone --depth 1 https://github.com/yildizberkay/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/yildizberkay/skills/react-i18next)<a href="https://agentmods.dev/skills/yildizberkay/skills/react-i18next"><img src="https://agentmods.dev/badge/skills/yildizberkay/skills/react-i18next/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/yildizberkay/skills/react-i18next"><img src="https://agentmods.dev/badge/skills/yildizberkay/skills/react-i18next.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.00177 | $0.03322 |
| Opus 5 | $0.00088 | $0.01661 |
| Sonnet 5 | $0.00035 | $0.00664 |
| Haiku 4.5 | $0.00018 | $0.00332 |
Grade A, and why
react-i18next 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 8d 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 — 407 lines — stays where its author put it; the contents beside it link to each section on GitHub.
react-i18next Skill
react-i18next is the standard internationalization framework for React / React Native, built on top of i18next. This skill covers setup, configuration, all API surfaces, and common patterns.
Key mental model: i18next is the core translation engine (config, plurals, interpolation, formatting). react-i18next is the React binding layer that connects i18next to your components via hooks, HOCs, render props, and the Trans component.
Installation
npm install react-i18next i18next --save
# Common companion packages:
npm install i18next-http-backend i18next-browser-languagedetector --save
i18next Configuration (i18n.js)
Create i18n.js beside your entry point. This is the single source of truth for your i18n setup.
Minimal setup (inline resources)
import i18n from 'i18next';
import { initReactI18next } from 'react-i18next';
i18n
.use(initReactI18next)
.init({
resources: {
en: {
translation: {
"welcome": "Welcome to our app"
}
},
tr: {
translation: {
"welcome": "Uygulamamıza hoş geldiniz"
}
}
},
lng: 'en', // default language
fallbackLng: 'en',
interpolation: {
escapeValue: false // React already escapes by default
}
});
export default i18n;
Production setup (with backend + language detection)
import i18n from 'i18next';
import { initReactI18next } from 'react-i18next';
import Backend from 'i18next-http-backend';
import LanguageDetector from 'i18next-browser-languagedetector';
i18n
.use(Backend) // loads translations from /public/locales/{lng}/{ns}.json
.use(LanguageDetector) // detects user language
.use(initReactI18next) // binds i18next to React
.init({
fallbackLng: 'en',
debug: true, // set false in production
interpolation: {
escapeValue: false
},
// react-specific options (all optional):
// react: {
// bindI18n: 'languageChanged',
// bindI18nStore: '',
// transEmptyNodeValue: '',
// transSupportBasicHtmlNodes: true,
// transKeepBasicHtmlNodesFor: ['br', 'strong', 'i', 'p'],
// useSuspense: true,
// }
});
export default i18n;
What ships with it
3 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.
- 8d ago First seen · 407 lines · 177 tokens per session scan A ad0cda8738f5
react-i18next is a skill published in the GitHub repository yildizberkay/skills (2 stars, last pushed 6mo ago), licensed Apache-2.0. It adds 177 tokens to every session and 3,322 once invoked, about $0.0009 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
json-ui
CRITICAL: Use for json-ui component rendering and development. Triggers on: json-ui, json render, component catalog, report render, HTML report, I18nString, i18n, bilingual, language switch, dual language, PaperHeader, AuthorList, Abstract, MetricsGrid, Section, Highlight, Zod schema, catalog.ts, cli.ts…
aksel-builder
Expert builder for Aksel, the Nav / @navikt design system — React components, design tokens, layout primitives, theming (light/dark), icons, CSS, the Tailwind preset, version migrations, Figma-to-code. Triggers — Aksel, "using/with aksel", Nav/Navikt, "designsystemet", "design system", @navikt/ds- (e.g.…
localization-toolkit
This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages…
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
intlayer-react
Integrates Intlayer internationalization with React component. Use when the user asks to "setup React i18n", create a new translated component, use the "useIntlayer" hook, or configure providers.
nextjs-on-cloudflare
Build, migrate, and deploy Next.js apps on Cloudflare Workers with vinext. Use when starting a Next.js project on Cloudflare, moving an existing app to Workers, choosing between vinext and OpenNext, or setting up vinext for Workers. For setup, migration, or deployment, install vinext's upstream skills with npx skills…