Borrowing it
Nothing to install: this file belongs to kikin81/nubecita. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kikin81/nubecita/main/.claude/skills/translate-strings/SKILL.mdgit clone --depth 1 https://github.com/kikin81/nubecitaWrote 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/kikin81/nubecita/translate-strings)<a href="https://agentmods.dev/skills/kikin81/nubecita/translate-strings"><img src="https://agentmods.dev/badge/skills/kikin81/nubecita/translate-strings/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/kikin81/nubecita/translate-strings"><img src="https://agentmods.dev/badge/skills/kikin81/nubecita/translate-strings.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.00117 | $0.02712 |
| Opus 5 | $0.00059 | $0.01356 |
| Sonnet 5 | $0.00023 | $0.00542 |
| Haiku 4.5 | $0.00012 | $0.00271 |
Grade A, and why
translate-strings 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.
This is a copy
81% identical to prototype — 149 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce repo-owned values-<qualifier>/strings.xml translations with consistent terminology, preserved format args/plurals, and hard verification. This is how you satisfy the MissingTranslation lint error (promoted in both convention plugins) — a new string can't ship without its translations.
Why repo-owned and not Play's free Gemini auto-translate: Play injects translations into the served bundle at release time with no export, so they can't feed a local/bench build or be screenshotted. Owning them in res/values-* gives a real localized app + diffable PRs + screenshottable UI.
Pick the mode
- New locale (full) — the locale has no
values-<qualifier>/yet. Translate every source string across all modules. Fan out (below). - Backfill (incremental) — the locale exists but is missing keys (a new string landed;
MissingTranslationfails). Translate only the missing keys and merge them in. Usually small — do it inline, no fan-out.
Locale → Android qualifier
Play/BCP-47 code → res/values-<qualifier>/:
| Locale | Qualifier folder | Notes |
|---|---|---|
es-419 |
values-b+es+419 |
numeric UN-M.49 region must use the BCP-47 b+ form (no -r form exists for 419) |
pt-BR |
values-pt-rBR |
2-letter region → legacy -r form (more backward-compatible) |
es / pt |
values-es / values-pt |
macro language (serves every region of that language) |
es-ES / pt-PT |
values-b+es+ES or values-es-rES / values-pt-rPT |
2-letter region → -r form works |
zh-Hans |
values-b+zh+Hans |
script subtag → b+ form |
The repo currently ships es-419 (values-b+es+419) and pt-BR (values-pt-rBR).
Find the work
# Source files (the English source of truth):
find . -name "strings.xml" -path "*/src/main/res/values/strings.xml" | grep -v "/build/"
# Backfill mode — keys missing in a locale, per module (QUAL = e.g. b+es+419):
keys() { grep -v 'translatable="false"' "$1" | grep -oE 'name="[^"]+"' | sort -u; }
for src in $(find . -name strings.xml -path "*/src/main/res/values/strings.xml" | grep -v /build/); do
dir=$(dirname "$(dirname "$src")"); loc="$dir/values-QUAL/strings.xml"
[ -f "$loc" ] && comm -23 <(keys "$src") <(keys "$loc") | sed "s#^#$src missing: #"
done
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 · 143 lines · 117 tokens per session scan A e45bd3d374cf
translate-strings is a skill published in the GitHub repository kikin81/nubecita (5 stars, last pushed today), licensed MIT. It adds 117 tokens to every session and 2,712 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 81% identical to prototype, differing in 149 lines, and is treated as a copy.
Other skills, from other repositories
flutter-setup-localization
Add flutterlocalizations and intl dependencies, enable "generate true" in pubspec.yaml, and create an l10n.yaml configuration file. Use when initializing localization support for a new Flutter project.
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
ios-marketing-capture
Use when the user wants to automate capture of marketing screenshots for a SwiftUI iOS app across multiple locales, devices, or appearances. Covers full-screen shots, isolated element renders (carousel cards, widgets), and reproducible output naming. Triggers on marketing screenshots, locale screenshots, widget…
maui-localization-theming
Implement MAUI localization and theming. USE FOR: RESX/AppResources, runtime culture switching, RTL/FlowDirection, platform language metadata, AppThemeBinding, DynamicResource, light/dark/system themes, UserAppTheme. DO NOT USE FOR: general layout, accessibility audits, icon/splash assets.
localization-l10n
Implement localization (l10n) best practices to adapt applications for specific regions, languages, and cultural preferences.