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 a554b554/Reactant --skill translategit clone --depth 1 https://github.com/a554b554/ReactantWrote 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/a554b554/reactant/translate)<a href="https://agentmods.dev/skills/a554b554/reactant/translate"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/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/a554b554/reactant/translate"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/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.00037 | $0.00448 |
| Opus 5.5 | $0.00015 | $0.00179 |
| Sonnet 5.5 | $0.00007 | $0.00090 |
| Haiku 4.5 | $0.00004 | $0.00045 |
Grade A, and why
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 1mo 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.
What it actually says
Translate
Activation Boundary
This is a tag-only worker skill. Use it only after execute or execute-one
selects an exact <@translate...> annotation in a target document. Never
activate it from ordinary chat, semantic similarity, or another non-router
skill. Without that handoff, change nothing.
Translate the surrounding block into the requested language, then consume the tag.
Tag
<@translate: target language>
Example: <@translate: German>.
Input
- File path — the document being processed.
- Surrounding block — the maximal run of non-blank lines containing the tag; blank lines bound it.
- Prompt — the target language, optionally with style notes.
Workflow
- Read the surrounding block; read the full file if terminology context helps.
- Translate the authored prose into the target language. Leave citation keys, code spans, and LaTeX commands untranslated.
- Write the result back: replace the surrounding block (including the
<@translate: ...>tag) with the translation.
Scope Modifiers
- Protect
<< >>— content stays in the original language, untouched; remove the delimiters in the output. - Field
(( ))— translate only inside the field; remove the delimiters in the output.
Context References
Double-backtick references in the prompt (for example a glossary file) are inputs; resolve paths relative to the document's directory unless absolute.
Rules
- Consume this tag and its consumed modifier delimiters. Preserve every
unrelated tag,
<@comment: ...>tag,<@chat-model>block, and contextual literal/example byte-for-byte. - If no target language is given or a referenced file is unreadable, fail cleanly: leave the tag, change nothing, report the error.
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.
- 1mo ago First seen · 61 lines · 37 tokens per session scan A c4d73931bb1c
translate is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 448 once invoked, about $0.0001 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-09-10.
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.
docs-governance
Use when writing, restructuring, auditing, or reviewing Cherry Studio repository documentation, READMEs, JSDoc, comments, Agent instructions, or paired English/Chinese docs, including source-linked documentation impact checks.