Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/landim32/awesome-ai-skillsnpx agentmods add skills/landim32/awesome-ai-skills/add-react-i18nWrote 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/landim32/awesome-ai-skills/add-react-i18n)<a href="https://agentmods.dev/skills/landim32/awesome-ai-skills/add-react-i18n"><img src="https://agentmods.dev/badge/skills/landim32/awesome-ai-skills/add-react-i18n/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/landim32/awesome-ai-skills/add-react-i18n"><img src="https://agentmods.dev/badge/skills/landim32/awesome-ai-skills/add-react-i18n.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.00052 | $0.03182 |
| Opus 5.5 | $0.00021 | $0.01273 |
| Sonnet 5.5 | $0.00010 | $0.00636 |
| Haiku 4.5 | $0.00005 | $0.00318 |
Grade A, and why
add-react-i18n 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 — 430 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add react-i18next to a React NPM Library Package
This skill adds internationalization (i18n) to a React NPM library package using react-i18next with an isolated i18n instance pattern that avoids conflicts with the consuming application's own i18n setup.
Arguments
default-language(optional): The default language code (e.g.,en,pt). Defaults toen.additional-languages(optional): Space-separated additional language codes to create translation files for (e.g.,pt es fr).
Overview
The implementation follows these principles:
- Isolated i18n instance — Uses
i18next.createInstance()instead of the global instance to prevent conflicts with the consuming app - Dedicated namespace — All library translations live under a unique namespace (derived from the package name) to avoid key collisions
- Consumer customization — The library's Provider accepts
languageandtranslationsprops so consumers can override/extend translations - Synchronous init — Uses
initImmediate: falseso translations are available immediately without async loading - Dynamic Zod schemas — Zod validation schemas are wrapped in factory functions +
useMemoto re-evaluate when language changes - Utility function i18n — Utility functions accept an optional
tparameter with English hardcoded fallback
Step-by-Step Instructions
Step 1: Analyze the Project
Before making any changes, thoroughly analyze the project structure:
-
Find the entry point — Read
package.jsonto find themain/modulefield, then read the entry file (usuallysrc/index.ts) to understand all public exports. -
Find the Provider/Context — Search for React Context providers. Look for patterns like:
Glob: src/**/Context*.tsx, src/**/Provider*.tsx, src/contexts/** Grep: createContext, Provider -
Find all components with hardcoded strings — Search for visible text:
Grep patterns: placeholder=", label, >.*</, title=", aria-label="Read each component and catalog all hardcoded strings (labels, placeholders, error messages, validation messages, button text, titles, etc.).
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 · 430 lines · 0 tokens per session scan A 395b0c6c2940
add-react-i18n is a skill published in the GitHub repository landim32/awesome-ai-skills (1 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 3,182 once invoked, about $0.0002 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-31.
Other skills, from other repositories
react-native-expert
Builds, optimizes, and debugs cross-platform mobile applications with React Native and Expo. Implements navigation hierarchies (tabs, stacks, drawers), configures native modules, optimizes FlatList rendering with memo and useCallback, and handles platform-specific code for iOS and Android. Use when building a React…
react-expert
Use when building React 18+ applications in .jsx or .tsx files, Next.js App Router projects, or create-react-app setups. Creates components, implements custom hooks, debugs rendering issues, migrates class components to functional, and implements state management. Invoke for Server Components, Suspense boundaries…
resume-cover-letter
Write a resume / CV or cover letter tailored to a specific role. Handles regional format differences (AU/NZ, US, UK), ATS-friendly formatting, achievement-focused bullets, and cover letter structure. Use whenever the user mentions a job application, resume, CV, cover letter, career document, applying for a role, or…
nz-business-english
New Zealand business English writing style for professional communications — warm, inclusive, EN-NZ spelling (colour, organise, centre). Use whenever the user is writing for a New Zealand audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to…
uk-business-english
British business English writing style for professional communications — polished, understated, EN-GB spelling (colour, organise, centre). Use whenever the user is writing for a British audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to drafting…
us-business-english
American business English writing style for professional communications — direct, action-oriented, EN-US spelling (color, organize, center). Use whenever the user is writing for an American audience: emails, chat messages, proposals, client communications, blog posts, web copy, or any business writing. Apply to…