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 skills add dazz/kostja94-marketing-skills --skill translationgit clone --depth 1 https://github.com/dazz/kostja94-marketing-skillsWrote 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/dazz/kostja94-marketing-skills/translation)<a href="https://agentmods.dev/skills/dazz/kostja94-marketing-skills/translation"><img src="https://agentmods.dev/badge/skills/dazz/kostja94-marketing-skills/translation/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/dazz/kostja94-marketing-skills/translation"><img src="https://agentmods.dev/badge/skills/dazz/kostja94-marketing-skills/translation.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.00079 | $0.02006 |
| Opus 5 | $0.00039 | $0.01003 |
| Sonnet 5 | $0.00016 | $0.00401 |
| Haiku 4.5 | $0.00008 | $0.00201 |
Grade A, and why
translation 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
100% identical to translation — 0 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content: Translation
Guides translation workflow, terminology, style, and quality for multilingual content. Covers when to use human vs machine translation, glossary and style guide creation, and SEO considerations. For i18n implementation, hreflang, and URL structure, see localization-strategy.
When invoking: On first use, if helpful, open with 1–2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope
- Workflow: Brief → translate → review
- Terminology: Glossary creation and management
- Style guide: Voice, tone, formatting per language
- Human vs MT: When to use each; post-editing
- Quality: QA, consistency, SEO
- Market-specific: Terminology by region
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for brand voice, target markets, and product terminology.
Identify:
- Content type: Product UI, marketing copy, blog, landing page, docs
- Target language(s): Priority locales
- Existing assets: Glossary, style guide, translation memory (TM)
1. Translation Workflow
Brief → Translate → Review
| Phase | Purpose | Output |
|---|---|---|
| Brief | Context, audience, tone, glossary reference, style guide | Translator brief document |
| Translate | First pass; use glossary + TM when available | Draft translation |
| Review | Native speaker review; consistency, brand voice, SEO | Final translation |
Translator Brief
Include in every project:
- Context: What the content is for (landing page, product UI, blog)
- Audience: Target market, user persona
- Tone: Formal, casual, technical
- Glossary: Link or attach; mandatory terms
- Style guide: Reference or key rules
- Constraints: Character limits (UI), SEO keywords to include naturally
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 · 223 lines · 79 tokens per session scan A 78f5d4dab638
translation is a skill published in the GitHub repository dazz/kostja94-marketing-skills (2 stars, last pushed 2mo ago), licensed MIT. It adds 79 tokens to every session and 2,006 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to translation, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
azure-ai-translation-text-py
Azure AI Text Translation SDK for real-time text translation, transliteration, language detection, and dictionary lookup. Use for translating text content in applications. Triggers: "text translation", "translator", "translate text", "transliterate", "TextTranslationClient".
harden
Improve interface resilience through better error handling, i18n support, text overflow handling, and edge case management. Makes interfaces robust and production-ready. Use when the user asks to harden, make production-ready, handle edge cases, add error states, or fix overflow and i18n issues.
seedance-vocab-ja
This skill should be used when the user asks for Japanese Seedance 2.0 prompt wording, Japanese cinematic vocabulary, or translation of camera, lighting, action, VFX, audio, and production terms into Japanese.
asc-subscription-localization
Bulk-localize subscription, subscription-group, and in-app purchase display names across App Store locales using asc, including API 4.4.1 version-scoped v2 resources. Use when filling or updating subscription/IAP names and descriptions without App Store Connect UI work.
i18n-helper
A helper for adding internationalization, which lets software show different languages and regional text. It finds user-visible text written directly in code and moves it into language files.