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 anhnguyen0905/codex-mcp --skill localization-copygit clone --depth 1 https://github.com/anhnguyen0905/codex-mcpWrote 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/anhnguyen0905/codex-mcp/localization-copy)<a href="https://agentmods.dev/skills/anhnguyen0905/codex-mcp/localization-copy"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/localization-copy/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/anhnguyen0905/codex-mcp/localization-copy"><img src="https://agentmods.dev/badge/skills/anhnguyen0905/codex-mcp/localization-copy.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.00102 | $0.01245 |
| Opus 5 | $0.00051 | $0.00622 |
| Sonnet 5 | $0.00020 | $0.00249 |
| Haiku 4.5 | $0.00010 | $0.00125 |
Grade A, and why
localization-copy 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Localization Copy (translating product and marketing text safely)
Pick the right mode per string
translation → preserve meaning, sentence by sentence (legal, docs, UI labels)
localisation → meaning plus locale conventions/references (most product UI, help)
transcreation → preserve intent and effect, rewrite freely (taglines, ads, names)
The commonest failure is applying translation where transcreation was needed: a wordplay headline rendered literally is not wrong word-by-word and still fails completely. Mark the mode on each string before it leaves, and brief transcreation with intent, audience and constraint (character limit, brand line), not with the source sentence alone.
Tone and register are part of the spec
Formality is grammatical in many languages (T–V distinction, honorific levels), so "friendly" is not portable — specify register per locale explicitly, including how the product addresses the user and whether imperatives read as rude, and hold it constant product-wide.
Glossary and do-not-translate
Keep a termbase with, per term: source term, approved target per locale, part of speech, short definition, forbidden alternatives. Keep a separate do-not-translate list: product and feature names, brands, trademarks, code identifiers, API field names, third-party UI labels seen verbatim, and units the market uses in source form. Without it, translators localise your own feature name and UI, docs and support macros diverge permanently.
Placeholder, variable and plural safety
Placeholders must reach the translator intact, reorderable and documented — state what {count}, %1$s
or {name} will hold, since the target may need a different word order. Never concatenate sentence
fragments in code: fragments cannot be reordered or inflected. Use ICU-style plural categories rather
than if n == 1; locales use different category sets (zero, one, two, few, many, other) that a
two-branch string cannot express — likewise gender and select variants. Validate mechanically:
identical placeholder set source-vs-target, no renamed tokens, no dropped markup.
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 · 96 lines · 102 tokens per session scan A 336609907fc6
localization-copy is a skill published in the GitHub repository anhnguyen0905/codex-mcp (3 stars, last pushed 6d ago), licensed MIT. It adds 102 tokens to every session and 1,245 once invoked, about $0.0005 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.