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 flukeatzerocool/infobroker --skill translationgit clone --depth 1 https://github.com/flukeatzerocool/infobrokerWrote 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/flukeatzerocool/infobroker/translation)<a href="https://agentmods.dev/skills/flukeatzerocool/infobroker/translation"><img src="https://agentmods.dev/badge/skills/flukeatzerocool/infobroker/translation.svg" alt="Measured on agentmods" 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.00042 | $0.00622 |
| Opus 5 | $0.00021 | $0.00311 |
| Sonnet 5 | $0.00008 | $0.00124 |
| Haiku 4.5 | $0.00004 | $0.00062 |
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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Translation
When NOT to Use
- For translating code logic or identifiers where the meaning must remain in English.
- When the user has not specified the target language or formality level.
Workflow
-
Analyze the source. Identify domain, register, audience, and format. Note idioms, cultural references, and placeholders.
-
Research terminology. Build a glossary for technical, legal, or domain-specific terms. Use the user's translation memory if available.
Infobroker Integration: Use
search_webwith Wiktionary or Wikipedia for domain terminology research. Usefetch_pagefor bilingual glossaries or parallel texts. -
Translate. Preserve meaning, tone, and formatting. Keep placeholders, code blocks, and HTML/Markdown structure intact.
-
Localize. Adapt units, dates, currency, and culturally bound metaphors to the target locale.
-
Review. Check grammar, fluency, and consistency. Ensure no sentences are omitted or duplicated.
-
Deliver with annotations. Return the translation in the same format. Include notes for ambiguous choices.
Best Practices
- Preserve structure, tags, and placeholders.
- Maintain terminology consistency across the document.
- Respect formality registers (e.g., tu vs. usted, casual vs. formal Japanese).
- Handle pluralization rules of the target language.
- Avoid literal translation of idioms.
Output Contract
Always end with a searchable one-line status:
translation complete. <target language> | <N> segments | structure preserved
<N> segments is the number of translated units. Replace
structure preserved with a list of any structure differences (omitted or
duplicated sentences, altered tags or placeholders) that the review
detected.
Edge Cases
- Untranslatable terms: Keep established technical terms in English and note the decision.
- Right-to-left languages: Use proper bidirectional markers for mixed text.
- CJK length issues: Flag translations that may exceed fixed-width UI fields.
- Gendered language: Ask for guidance or provide variants when the source is gender-neutral.
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 Changed fe6fef43e32d
- 7d ago First seen · 82 lines · 42 tokens per session scan A 46015461f5fc
translation is a skill published in the GitHub repository flukeatzerocool/infobroker (0 stars, last pushed yesterday), licensed MIT. It adds 42 tokens to every session and 622 once invoked, about $0.0002 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
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.