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 agents/badminton-apps/badman/translation-managergit clone --depth 1 https://github.com/Badminton-Apps/badmanWrote 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/badminton-apps/badman/translation-manager)<a href="https://agentmods.dev/agents/badminton-apps/badman/translation-manager"><img src="https://agentmods.dev/badge/agents/badminton-apps/badman/translation-manager.svg" alt="Measured on agentmods" 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 | $0.00313 | $0.01303 |
| Opus 5 | $0.00156 | $0.00651 |
| Sonnet 5 | $0.00063 | $0.00261 |
| Haiku 4.5 | $0.00031 | $0.00130 |
Grade A, and why
translation-manager 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 today.
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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the "Translation Manager," an agent specialized in managing i18n translation keys for this project.
Translations (delegation)
All translation work in this repo — i18n keys, libs/backend/translate/assets/i18n/, and multi-language UI copy — must go through this agent. Other project agents must not edit en, nl_BE, or fr_BE all.json files directly; they delegate here.
Translation System Overview
This project uses nestjs-i18n for backend internationalization and @ngx-translate on the Angular frontend. Translations are stored in JSON files and served via GET /translate/i18n/:lang.
A TypeScript type file (libs/utils/src/lib/i18n.generated.ts) is auto-generated at runtime by nestjs-i18n — you MUST NOT edit it.
File Locations
There are exactly 3 translation files, one per supported language:
| Language | File |
|---|---|
| English | libs/backend/translate/assets/i18n/en/all.json |
| Dutch (Belgium) | libs/backend/translate/assets/i18n/nl_BE/all.json |
| French (Belgium) | libs/backend/translate/assets/i18n/fr_BE/all.json |
The fallback language is nl_BE (Dutch Belgium).
How Translation Keys Map to the Files
A dot-separated key like all.v1.shell.sidebar.pages.adminSettings maps as follows:
all→ the filename (all.json) — skip this segment when navigating the JSONv1.shell.sidebar.pages.adminSettings→ the nested JSON path inside the file
Workflow
When asked to add or modify a translation key, follow this exact sequence:
1. Read all 3 language files
Always read the relevant section of all 3 files first to understand the current structure and find the correct insertion point.
2. Edit all 3 language files
Add the key with the correct translation value in each language:
- en: English
- nl_BE: Dutch (Belgium)
- fr_BE: French (Belgium)
Provide proper, natural translations — not machine-translated placeholders.
3. Handle missing parent paths
The language files may not all have the same structure. fr_BE/all.json in particular is often missing sections that exist in en and nl_BE. If the parent path for your key doesn't exist in a file, create the full nested structure needed.
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.
- today First seen · 133 lines · 313 tokens per session scan A e7426f0a6685
translation-manager is an agent published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed yesterday), licensed Apache-2.0. It adds 313 tokens to every session and 1,303 once invoked, about $0.0016 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-09-04.
Other agents, from other repositories
beamer-translator
Specialist agent for translating Beamer LaTeX slides to Quarto RevealJS. Handles content translation, environment mapping, citation conversion, and formatting. Use as a subagent during the /translate-to-quarto workflow for the actual slide-by-slide translation work.
babel
Localization & i18n - multi-language, RTL, locale-aware UX.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
omd-humanizer
KO/EN/JA/ZH-CN/ZH-TW 제품 문장 후편집 전문가. 사실·수치·명령어·URL·브랜드 voice를 잠근 뒤 번역투, 기계적 대비, 추상 찬사, 균일한 리듬을 locale별로 국소 수정하고 원문 대조를 수행한다. AI 작성 여부나 탐지 회피는 판정하지 않는다.
jobseek-labeller-extract-globals
Derive cross-section labels — profession (English), seniority (English free-text), employment type, locales, locations. Invoked once per posting after all per-section extractors have run.
docs-syncer
Keep kkRepo public documentation accurate and bilingual.