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/bloombooks/bloomdesktop/xlf-stringsnpx skills add BloomBooks/BloomDesktop --skill xlf-stringsgit clone --depth 1 https://github.com/BloomBooks/BloomDesktopWrote 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/bloombooks/bloomdesktop/xlf-strings)<a href="https://agentmods.dev/skills/bloombooks/bloomdesktop/xlf-strings"><img src="https://agentmods.dev/badge/skills/bloombooks/bloomdesktop/xlf-strings.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 | $0.00016 | $0.01901 |
| Opus 5 | $0.00008 | $0.00950 |
| Sonnet 5 | $0.00003 | $0.00380 |
| Haiku 4.5 | $0.00002 | $0.00190 |
Grade A, and why
xlf-strings 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 4d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Apply this skill whenever you add a new localizable string to the codebase, modify an existing one, or review XLF files as part of a task.
This skill is the how — the procedure for each operation. The why — how Crowdin actually
works and what each kind of edit does to existing translations — lives in one place,
DistFiles/localization/README.md. Where a rule here has a reason, that reason is written there
and cited from here rather than restated, so the two can't drift into telling you different
things. Read its "Why we can't just delete a string" section before you conclude that any
deletion or id change is harmless.
Files
Localizable strings live in DistFiles/localization/en/. Only ever add or change strings in the English subdirectory — never touch the other language folders.
There are three priority files. Choose based on what the string labels:
| File | Use for |
|---|---|
Bloom.xlf |
The most important things in our UI that users must understand |
BloomMediumPriority.xlf |
Secondary options, help text, feature-specific instructions, important error messages |
BloomLowPriority.xlf |
Rarely-seen text like error messages |
Strings that are only meant to be seen by developers or if code bugs occur should not be localized. Add comments explaining why they are not.
Adding a new entry
- Ask the user which priority file to use, with your recommendation. Explain why you prefer one based on the table above. You may present several strings as a single question if they occur in the same context.
- Add the entry in the chosen file:
<trans-unit id="Namespace.EntryName" translate="no">
<source xml:lang="en">The English text</source>
<note>ID: Namespace.EntryName</note>
</trans-unit>
- Always mark new entries
translate="no"unless instructed otherwise. - Choose an ID in the form
Namespace.EntryNamethat matches the feature area.
Translator context notes
After the <note>ID: ...</note> line, add a second <note> whenever a translator would not have enough context from the string alone. This is required when the string is any of:
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.
- 4d ago First seen · 130 lines · 16 tokens per session scan A edba0717306b
xlf-strings is a skill published in the GitHub repository BloomBooks/BloomDesktop (44 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 1,901 once invoked, about $0.0001 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.
Other skills, from other repositories
planning-with-files-ar
تخطيط مستمر قائم على الملفات لعمل وكلاء الذكاء الاصطناعي متعدد الخطوات. يحتفظ بملفات taskplan.md و findings.md و progress.md على القرص، وتحقن خطافات دورة الحياة سياق التخطيط المحدد للمشروع. تقرأ الاستعادة التلقائية ملفات تخطيط المشروع فقط. يمكن للأمر الصريح session-catchup.py --metadata فحص بيانات وصفية لجلسات الوكيل…
kl-consistency-test
Write, calibrate, and debug the prefill-vs-decode logprob (KL) consistency tests in sglang -- the two independent conditions a zero requires (every operator batch-invariant, and the two paths computing the same function), which helper separates them, how to pick a threshold once they hold, and how to localize a…
i18n-localization
Internationalization and localization patterns. Detecting hardcoded strings, managing translations, locale files, RTL support.
baoyu-youtube-transcript
Downloads YouTube video transcripts/subtitles and cover images by URL or video ID. Supports multiple languages, translation, chapters, and speaker identification. Caches raw data for fast re-formatting. Use when user asks to "get YouTube transcript", "download subtitles", "get captions", "YouTube字幕", "YouTube封面"…
switchyard-rust-review
Review Switchyard Rust changes for correctness and maintainability. Use for pull requests or diffs touching crates, PyO3 bindings, async runtime behavior, streaming, protocol types, translation, algorithms, or LLM clients.
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.