What is blog-translator?

A translation and localization agent for blog posts, including Markdown, MDX, HTML, metadata, structured search data, and charts. Localization adapts wording, search terms, numbers, dates, currencies, and quotes for a target language and region.

Translating blog content, metadata, schema data, images’ alternative text, and formatted technical content into one or more target languages.

It preserves the source format while making the result sound native and remain useful for search engines. It also keeps language-specific SEO details from being translated mechanically.

blog-translator — Agent for Claude Code by Infrasity-Labs

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Infrasity-Labs/dev-gtm-claude-skills

Made for: Claude Code.

Or install marketing-skills, the plugin that ships this one along with the rest of its 116 skills, 8 commands, 23 agents, 1 hook.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/infrasity-labs/dev-gtm-claude-skills/blog-translator/github.svg)](https://agentmods.dev/agents/infrasity-labs/dev-gtm-claude-skills/blog-translator)

Your own site

<a href="https://agentmods.dev/agents/infrasity-labs/dev-gtm-claude-skills/blog-translator"><img src="https://agentmods.dev/badge/agents/infrasity-labs/dev-gtm-claude-skills/blog-translator/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/infrasity-labs/dev-gtm-claude-skills/blog-translator"><img src="https://agentmods.dev/badge/agents/infrasity-labs/dev-gtm-claude-skills/blog-translator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 105 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,454 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00105	$0.01454
Opus 5	$0.00053	$0.00727
Sonnet 5	$0.00021	$0.00291
Haiku 4.5	$0.00011	$0.00145

Measured 12d ago against content hash 928016738dbe, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

blog-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 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.

.claude/agents/blog-translator.md · 167 lines

How it starts

The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Blog Translator Agent

You are a specialized blog translation and localization agent. Your role is to produce native-quality translations of blog content optimized for both human readers and search engines.

Core Identity

You are not a generic translator. You are an SEO-aware content localizer. Every translation decision considers:

Does a native speaker write it this way?
Will search engines find this for the right local queries?
Are SEO elements (meta, alt, schema) independently optimized for the target locale, not mechanically translated?

When to Invoke

Spawn this agent from:

blog-translate (one agent per target language, run in parallel).
blog-multilingual (delegated through blog-translate).

One invocation handles one source-to-target language pair. To translate into N languages, spawn N agents.

Inputs Expected

The orchestrator provides:

source_file, absolute path to the source blog post.
target_lang, ISO 639-1 code (e.g. de, fr, pt-BR).
source_lang, ISO 639-1 code, autodetected if missing.
keyword_map, optional, decisions about which terms stay in the source language (loanwords) and which get a localized equivalent.
cultural_profile_ref, optional path to the matching profile in skills/blog-translate/references/cultural-adaptation.md.
output_path, where to write the translated file.

If any of these are missing, derive them by reading the source file's frontmatter and the orchestrator's invocation context.

Process

Step 1: Analyze the Source

Read the source file. Extract:

Title, meta description, all headings, body paragraphs.
Image alt text and <figcaption> content.
FAQ questions and answers.
Citation capsule text.
SVG chart <text> and <tspan> content.
CTA text.
Key Takeaways or summary box.
Internal-link zone anchor text (translate the anchor, not the marker).

Identify what to preserve unchanged: markdown and HTML structure, image URLs, link URLs, frontmatter keys, code blocks (translate inline comments only when meaningful prose), SVG attributes, schema structural keys, and internal-link zone markers ([INTERNAL-LINK: ...]).

Read the full file on GitHub · 167 lines

Changes

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 · 167 lines · 105 tokens per session scan A 928016738dbe

Subscribe to this mod's changes

blog-translator is an agent published in the GitHub repository Infrasity-Labs/dev-gtm-claude-skills (124 stars, last pushed 2mo ago), licensed MIT. It adds 105 tokens to every session and 1,454 once invoked, about $0.0005 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.

Localization Writing and docs ai-citation ai-visibility claude claude-skills dev-gtm geo

harvest-worker

Grounded recon for ONE audience segment — gathers real, signal-backed user queries and returns validated QuestionCandidate JSON. Never writes questions.csv, never touches the DB. Spawned by the open-geo orchestrator (STEP A.5, Phase A).

Pupok462/open-geo · 54 tokens

core-worker

Builds ONE measured demand cluster family for a semantic core — expands seeds through the demand APIs, phrases the assistant prompts, and returns validated CoreCluster JSON. No browser, never writes the core or the CSV. Spawned by the semantic-core orchestrator (STEP 4).

Pupok462/open-geo · 58 tokens

translate-junior

Haiku-tier worker for the translator panel. Translates ONLY pure, low-risk UI chrome — nav labels, buttons, footer links, error messages, generic form labels, language-switcher entries, and plain single-word/short microcopy in message catalogs (JSON, .po/.pot, .ts/.js, .arb, etc.). Never touches domain terminology…

roshaw/claude-translation-agency · 148 tokens

blog-translator