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 agentmods add commands/osiris-devworks/smart-citizen/language_support_checkgit clone --depth 1 https://github.com/Osiris-DevWorks/smart-citizenWhat 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 | $0.00021 | $0.01488 |
| Opus 5 | $0.00010 | $0.00744 |
| Sonnet 5 | $0.00004 | $0.00298 |
| Haiku 4.5 | $0.00002 | $0.00149 |
Grade A, and why
language_support_check 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 2d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/language_support_check
Audit translation coverage for every activated language. Catches the gaps the i18n fallback chain hides: a key that silently renders in English because it was never added to a language file, a new dialog whose strings were added to english/ui.json only, an in-app doc that never got a translated copy, and hardcoded literals that bypass tr() entirely and can never be translated.
Background: tr() resolves each key as ht (human translation), then at (AI translation), then the English base value, then the bare key. "Has at least the AI translation" means every key shows something in the selected language: ht or at non-empty. Provenance rules live in languages/TRANSLATIONS.md.
Policy constraints (read before drafting anything)
- Never edit or overwrite a non-empty
ht. Human translations are only ever replaced by better human translations. - AI backfill happens only at pre-release docs-sync time, with explicit confirmation. This command surfaces gaps; it does not fill them unless the user says so at the checkpoint.
- New AI translations go in
at(leavehtempty) so the inline provenance stays truthful and translators can find them withgrep '"ht": ""'.
Inputs
languages/<lang>/ui.jsonfor every activated language. Activated = whatAppSettings.get_available_languages()(src/utils/settings.py) offers: English plus any folder whoseui.jsoncarries at least one translation.languages/english/ui.jsonis the key universe; every leaf there is a key the UI can request.languages/<lang>/HELP.md,ABOUT.md,LEGAL.md: per-language in-app docs, resolved byAppSettings.get_localized_doc_path(). A missing file falls back to the Englishdocs/copy.languages/sources.json: per-language base.ini download URL for game strings.installer.iss: theLanguageChoicePageoption list and theselected_languageregistry write-back values.src/gui/*.py: user-facing literals, to catch strings not routed throughtr().SmartCitizen.specandscripts/build/build_exe.py: both bundling lists must ship thelanguages/tree (a file present in the repo but missing from either list breaks only the frozen build).
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.
- 2d ago First seen · 71 lines · 21 tokens per session scan A b8cc15b1d0e6
language_support_check is a command published in the GitHub repository Osiris-DevWorks/smart-citizen (99 stars, last pushed 4d ago), licensed Apache-2.0. It adds 21 tokens to every session and 1,488 once invoked, about $0.0001 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-30.
Other commands, from other repositories
translation-review
全面审核翻译质量: 对比原版、专项检查、质量评分与发布验证, 发现问题时自动衔接修复流程.
translation-fix
智能修复翻译问题和质量缺陷, 可独立使用或由 /translation-review 自动衔接调用.
language
Command "language" from ErisPulse/ErisPulse, covering erispulse.cli.commands.language 模块, 模块概述, 类列表 and class languagecommand(command).
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
auto
Manage language auto-detection settings.
brand-update
Recalibrate the brand pack after positioning, personas, pricing or naming changed — propagate the change through terminology, strings and every locale in the same edit.