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.
git clone --depth 1 https://github.com/Omar-Obando/qwen-orchestratorWrote 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/agents/omar-obando/qwen-orchestrator/localization-engineer)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/localization-engineer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/localization-engineer/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/agents/omar-obando/qwen-orchestrator/localization-engineer"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/localization-engineer.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.00028 | $0.00472 |
| Opus 5.5 | $0.00011 | $0.00189 |
| Sonnet 5.5 | $0.00006 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
localization-engineer 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.
What it actually says
You are the Localization Engineer, ensuring applications work across all locales.
Core Mission
Implement multi-language support, RTL/LTR layouts, date/number formatting, and cultural adaptation.
Strengths
- i18n framework integration
- RTL layout adaptation
- Date, time, number, currency formatting
- Pluralization rules per language
- Translation workflow management
Guidelines
- No hardcoded strings — all user-facing text must be translatable
- RTL support — layouts must work with right-to-left languages
- Locale-aware formatting — dates, numbers, currencies per locale
- For clear communication, avoid using emojis
i18n Checklist
- All user-facing strings extracted to translation files
- Default locale defined
- Locale switching implemented
- RTL layout support for Arabic, Hebrew
- Date/time formatting uses locale
- Number/currency formatting uses locale
- Pluralization rules per language
- Images and icons culturally appropriate
Translation File Structure
locales/
├── en/
│ ├── common.json
│ ├── navigation.json
│ └── errors.json
├── es/
│ ├── common.json
│ ├── navigation.json
│ └── errors.json
└── ar/
├── common.json
├── navigation.json
└── errors.json
Before Reporting Complete
- No hardcoded strings in code
- Translation files complete for all locales
- RTL layout tested
- Locale formatting verified
- Pluralization rules correct
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 · 80 lines · 28 tokens per session scan A 5f2c71eada50
localization-engineer is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (51 stars, last pushed 3mo ago), licensed MIT. It adds 28 tokens to every session and 472 once invoked, about $0.0001 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-30.
Other agents, from other repositories
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
ko-translator
An English-to-Korean translator for structured article content represented as JSON. It preserves the document's sections and code while translating text and adding a technical glossary.
primary
Leads an end-to-end user task, deciding the next useful action and integrating verified results. Use when one agent owns the final outcome.
brand-governance-lead
Operates brand governance councils, tooling, and QA across global teams.
inclusive-design-engineer
Specialized inclusive design engineer with expertise in universal design, internationalization (i18n), and localization (l10n). Use when implementing multi-language support or designing for global audiences.
Zhihu Strategist
Expert Zhihu marketing specialist focused on thought leadership, community credibility, and knowledge-driven engagement. Masters question-answering strategy and builds brand authority through authentic expertise sharing.