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 skills/localplugins/plugins/transcreationnpx skills add localplugins/plugins --skill transcreationgit clone --depth 1 https://github.com/localplugins/pluginsWhat 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.00082 | $0.01178 |
| Opus 5 | $0.00041 | $0.00589 |
| Sonnet 5 | $0.00016 | $0.00236 |
| Haiku 4.5 | $0.00008 | $0.00118 |
Grade A, and why
transcreation 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 yesterday.
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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Transcreation
Overview
Transcreation adapts content into another language so it feels native, preserving intent, brand voice, and emotional impact rather than translating literally. The wording is reworked; the effect is kept.
Literal translation breaks marketing: idioms fall flat, humor is lost, and register goes wrong. This skill loads the base brand profile and the target locale's overrides, reworks the copy for that market, protects do-not-translate glossary terms, and re-checks compliance and channel limits for the new language. It is instruction-driven and writes localized files, with no accounts, keys, or network access.
Prerequisites
- Source content to localize and one or more target locales in
xx-XXform (for examplede-DE,ja-JP). - The base brand profile plus any
content/brand/locales/<xx-XX>/overrides. The skill uses Glob and Read to find and load them and Write to save each localized asset. - The
style-guide.mdglossary section (Product and Trademark Names) for do-not-translate terms, and the locale'scompliance.mdfor market-specific rules.
Instructions
- Read the base brand files, then read any
locales/<xx-XX>/overrides. Locale rules win for that market. - Adapt, do not translate: rework idioms, humor, and references into locale equivalents, keeping the effect rather than the words.
- Set the register: choose the correct formality and honorifics for the persona and locale (Sie or du, keigo, tu or usted).
- Convert locale specifics: units, currency, date and number formats, names, and examples.
- Protect the glossary: never translate product names, trademarks, or taglines unless the brand supplies a sanctioned translation.
- Check the channel limit: text expands or contracts across languages, so re-fit each asset with the
channel-formatsspec. - Verify compliance against the locale's
compliance.md: disclaimers and prohibited terms can differ by country. - Handle scripts: apply right-to-left rules for Arabic and Hebrew and correct spacing for CJK.
- When asked, emit a back-translation plus a short note on adaptation choices so a non-native approver can sign off.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- yesterday First seen · 91 lines · 82 tokens per session scan A d06bac3b611d
transcreation is a skill published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 1,178 once invoked, about $0.0004 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 skills, from other repositories
code-to-content
Use when transforming a codebase into developer content. Activates for: Blog posts, tutorials, or technical documentation about code README, changelog, release notes, or API docs generation Twitter/X threads, LinkedIn posts about technical work Conference talk proposals (CFP) or newsletter content Build-in-public…
Chinese Market Content Engineer
Generate, localize, and optimize content for Chinese digital platforms (微信公众号, 小红书, 抖音, 知乎, B站) with cultural nuance and platform-specific best practices.
audience-tailoring
Use this skill when the user asks to "tailor this for different audiences", "write this for an exec vs. engineering", "adapt this message for different stakeholders", "translate this for a non-technical audience", "help me communicate this to [specific role]", or has an existing document or message and wants to…
eng-brief
Use this skill when the user asks to "write an engineering brief", "brief the engineering team", "write a technical spec handoff", "summarize this PRD for engineers", "engineering kickoff doc", "write a spec for the dev team", "help me communicate this feature to engineering", or needs to translate a product decision…
brainstorm-okrs
Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.
pre-mortem
Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go…