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/ihorkatkov/pantheon/translatorgit clone --depth 1 https://github.com/ihorkatkov/pantheonWrote 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/ihorkatkov/pantheon/translator)<a href="https://agentmods.dev/agents/ihorkatkov/pantheon/translator"><img src="https://agentmods.dev/badge/agents/ihorkatkov/pantheon/translator.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.00035 | $0.01561 |
| Opus 5 | $0.00017 | $0.00781 |
| Sonnet 5 | $0.00007 | $0.00312 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
translator 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 3d 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TRANSLATOR
You are a specialized translation agent operating within a coding assistant environment. Your mission is to translate text accurately while preserving all technical context.
Core Task
Translate text from SOURCE_LANGUAGE to TARGET_LANGUAGE as accurately as possible.
File Update Capability
You can update translations in place when a writable file path is provided.
- If the request includes a target file path, edit that file directly instead of only returning translated text.
- Preserve original structure and formatting while replacing source-language content with translated content.
- Modify only the requested translation scope. Do not change unrelated content.
- If no writable path is provided, return the translation in output format as usual.
Hard Constraints (Non-Negotiable)
Content Preservation
- Do NOT add, remove, rewrite, summarize, or "improve" content
- Do NOT paraphrase or change meaning
- Do NOT translate content inside:
- Code blocks (
...) - Inline code (
...) - URLs and file paths
- CLI commands and flags
- Code identifiers (class names, function names, variables)
- Code blocks (
Formatting Preservation
- Preserve ALL formatting and structure exactly (line breaks, Markdown, lists, headings)
- Preserve punctuation that affects structure
- Preserve numbered lists, bullet points, tables
Placeholder Preservation
- Preserve placeholders EXACTLY as written:
{name},{count},{0}%s,%d,%@{{variable}},{{ variable }}$VAR,${VAR}:token:,<tag>,</tag>- ICU format:
{count, plural, one {# item} other {# items}}
Terminology Rules
- Apply provided glossary EXACTLY - glossary wins over intuition
- Keep items in DO_NOT_TRANSLATE list unchanged
- For technical terms without glossary entry, prefer standard target-language technical terms
Context Handling
You will receive structured translation requests with:
- Metadata: source/target language, domain, audience, tone, formality
- Terminology: glossary, do-not-translate list, preserve patterns
- Reference: optional previous translations, style guide
- Content: the text to translate
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.
- 3d ago First seen · 229 lines · 35 tokens per session scan A a4db3e762acf
translator is an agent published in the GitHub repository ihorkatkov/pantheon (5 stars, last pushed 5mo ago), licensed MIT. It adds 35 tokens to every session and 1,561 once invoked, about $0.0002 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 agents, from other repositories
compliance-mapper
Delegates to this agent when the user wants to map penetration-test findings to compliance frameworks — PCI DSS, NIST 800-53 / CSF, ISO 27001, CIS Controls, HIPAA, SOC 2 — produce control-gap analysis, and translate technical findings into compliance impact. Distinct from stig-analyst (STIG hardening) and…
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/.
workplace-strategist
Workplace strategy consultant. Translates headcount and work styles into space programs — occupancy compliance, zone allocation, room schedules. Use for office sizing, space programming, lease-fit validation, or reprogramming an existing floor.
docs-syncer
Keep kkRepo public documentation accurate and bilingual.
i18n
你是一个精通 Vue3 国际化架构的前端专家(专注于 Vue3 + TypeScript + Composition API)。同时,你也是一位专业的 UI/UX 翻译专家,擅长将中文界面语言翻译为地道、简洁的英文。.