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 teachskillofskills-ai/ContentForge-techshu --skill cf-translategit clone --depth 1 https://github.com/teachskillofskills-ai/ContentForge-techshuWrote 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/teachskillofskills-ai/contentforge-techshu/cf-translate)<a href="https://agentmods.dev/skills/teachskillofskills-ai/contentforge-techshu/cf-translate"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-translate/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/teachskillofskills-ai/contentforge-techshu/cf-translate"><img src="https://agentmods.dev/badge/skills/teachskillofskills-ai/contentforge-techshu/cf-translate.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.00163 | $0.03559 |
| Opus 5 | $0.00081 | $0.01780 |
| Sonnet 5 | $0.00033 | $0.00712 |
| Haiku 4.5 | $0.00016 | $0.00356 |
Grade A, and why
cf-translate 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 10d 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 cf-translate — 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Content Translation — Multilingual Publishing
Translate publication-ready ContentForge content into 15 languages while preserving brand voice integrity, citation accuracy, and SEO optimization. Three localization levels let you control the depth of cultural adaptation.
When to Use
Use /contentforge:cf-translate when you need:
- Translated content for international markets (15 languages)
- Brand-consistent multilingual content that matches your source voice in the target language
- SEO-localized content with keywords adapted for target market search behavior
- Citation-safe translations where URLs, source references, and inline citations remain intact
- Cultural adaptation beyond word-for-word translation (adapted or transcreated levels)
Prerequisite: Content must be produced (or imported) through the ContentForge pipeline first. Raw untreated content should go through /contentforge:create-content before translation.
Supported Languages
| Code | Language | Direction | Notes |
|---|---|---|---|
es |
Spanish | LTR | Spain + Latin America variants |
fr |
French | LTR | France + Canadian French |
de |
German | LTR | Compound word handling |
pt |
Portuguese | LTR | Brazil + Portugal variants |
it |
Italian | LTR | |
nl |
Dutch | LTR | |
ja |
Japanese | LTR | Honorifics and formality levels |
zh |
Chinese (Simplified) | LTR | Simplified by default, Traditional on request |
ko |
Korean | LTR | Honorific levels mapped to brand formality |
ar |
Arabic | RTL | Right-to-left layout considerations |
hi |
Hindi | LTR | Devanagari script handling |
ru |
Russian | LTR | |
pl |
Polish | LTR | |
tr |
Turkish | LTR | |
vi |
Vietnamese | LTR | Diacritics preservation |
Localization Levels
Literal (Level 1)
Word-for-word structural translation. Preserves the exact document structure, sentence order, and paragraph boundaries. Translates meaning accurately but does not adapt cultural references, humor, or idiomatic expressions.
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.
- 10d ago First seen · 282 lines · 163 tokens per session scan A 8497ade49bd7
cf-translate is a skill published in the GitHub repository teachskillofskills-ai/ContentForge-techshu (1 stars, last pushed 21d ago), licensed MIT. It adds 163 tokens to every session and 3,559 once invoked, about $0.0008 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cf-translate, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
hreflang-international
International / multilingual SEO audit focused on hreflang correctness. Detects and diagnoses the most common (and ranking-damaging) hreflang mistakes: missing or broken return tags, wrong language/region codes, missing x-default, self-referencing errors, conflicts between hreflang and canonical, and inconsistent…
react-i18n
Use when implementing translations in a React app (not Next.js) with react-i18next — useTranslation, namespaces, pluralization, Suspense.
laravel-i18n
Use when implementing Laravel translations — (), transchoice(), lang files, pluralization, locale middleware, or formatting.
translation-accuracy-reviewer
Compares a source text against its translation, flags potential inaccuracies and mistranslations, and explains each issue so an editor can make an informed correction.
nextjs-i18n
Use when implementing i18n in Next.js 16 — next-intl or DIY dictionaries, locale routing, language switch, or formatters.
astro-i18n
Use when implementing i18n in Astro — locale routing strategies, getRelativeLocaleUrl/getAbsoluteLocaleUrl, Astro.currentLocale, or hreflang with sitemap.