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 canvora/canvora-mcp --skill multilingual-campaigngit clone --depth 1 https://github.com/canvora/canvora-mcpWrote 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/canvora/canvora-mcp/multilingual-campaign)<a href="https://agentmods.dev/skills/canvora/canvora-mcp/multilingual-campaign"><img src="https://agentmods.dev/badge/skills/canvora/canvora-mcp/multilingual-campaign/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/canvora/canvora-mcp/multilingual-campaign"><img src="https://agentmods.dev/badge/skills/canvora/canvora-mcp/multilingual-campaign.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.00075 | $0.00912 |
| Opus 5.5 | $0.00030 | $0.00365 |
| Sonnet 5.5 | $0.00015 | $0.00182 |
| Haiku 4.5 | $0.00007 | $0.00091 |
Grade A, and why
multilingual-campaign 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multilingual campaign creation
The canonical flow: generate the campaign once, then convert it per
language. Canvora's localization converts the finished visuals image to
image: layout, colors, fonts and imagery stay exactly the same; only the text
changes language. Design effort happens once, in the master; every language
inherits it. The generate loop and credits: see the canvora skill. Don't
art-direct slide by slide, but do carry through any overall look the user has
stated.
The flow
- Generate the master once (usually in the user's primary market's
language) with the normal loop:
chat→ show the plan →confirm_generation→ pollget_generationuntilcompleted. - Confirm the language list with the user, then call
localize_generationwith the master'sgeneration_idandlanguages(up to 10 per call, named the way the market means them, e.g. "Brazilian Portuguese"). - It returns one generation ID per language: poll each with
get_generation.
localize_generation converts ALL visuals in the generation: 10 credits per
visual per language (a 6-slide deck into Spanish = 60). To convert only ONE
visual out of a multi-visual generation, use edit_image on that visual with
operation: "text" and "Translate all visible text into Spanish".
Add up the whole plan: master + (visuals × 10 × languages). State that total in the same message as the run: announce it, don't ask permission (the language list is the thing you confirm, not the price).
Briefing the master so conversions survive
- Short text: translations expand (German/Portuguese commonly +20–35%). Keep master slide text ≤20 words per slide; overflow in the converted versions is the #1 multilingual failure.
- Pin what shouldn't move: brand names, product names and campaign hashtags stay in the source language; say so in the brief ("keep 'Acme' and '#AcmeLaunch' untranslated").
- Language precision at conversion time: "Brazilian Portuguese" vs "Portuguese"; Simplified vs Traditional Chinese. Use what the user's market actually means.
- RTL check: Arabic/Hebrew/Urdu conversions handle text direction automatically; still check reading order on multi-column layouts before shipping.
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 Changed · +19 lines 0f55b6dd8f0a
- 2mo ago First seen · 64 lines · 75 tokens per session scan A abf3cbecd819
multilingual-campaign is a skill published in the GitHub repository canvora/canvora-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 75 tokens to every session and 912 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
simple-english
Rewrite text to ASD-STE100 Simplified Technical English.
website-maintainer
Use this skill when working on the Repomix documentation website in website/ directory, including VitePress configuration, multi-language content, or translation workflows.
rowboat-spaces
How to work as a member of Rowboat Spaces, the team chat where people and agents work together. Load it once per session, before acting on any request that reaches you from Rowboat; it covers your setup, mentions and hand-offs, the tools, and files.
azure-ai-translation-document-py
Azure AI Document Translation SDK for batch translation of documents with format preservation. Use for translating Word, PDF, Excel, PowerPoint, and other document formats at scale. Triggers: "document translation", "batch translation", "translate documents", "DocumentTranslationClient".
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".
azure-ai-translation-ts
Build translation applications using Azure Translation SDKs for JavaScript (@azure-rest/ai-translation-text, @azure-rest/ai-translation-document). Use when implementing text translation, transliteration, language detection, or batch document translation.