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 khasky/awesome-agent-skills --skill awesome-translate-ru-engit clone --depth 1 https://github.com/khasky/awesome-agent-skillsWrote 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/khasky/awesome-agent-skills/awesome-translate-ru-en)<a href="https://agentmods.dev/skills/khasky/awesome-agent-skills/awesome-translate-ru-en"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-translate-ru-en/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/khasky/awesome-agent-skills/awesome-translate-ru-en"><img src="https://agentmods.dev/badge/skills/khasky/awesome-agent-skills/awesome-translate-ru-en.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.02568 |
| Opus 5 | $0.00046 | $0.01284 |
| Sonnet 5 | $0.00018 | $0.00514 |
| Haiku 4.5 | $0.00009 | $0.00257 |
Grade A, and why
awesome-translate-ru-en 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Translate Russian → English
Translate Russian text into natural English that reads as if a native English speaker wrote it. Preserve every structural and non-prose element of the source byte-for-byte, and never re-introduce AI-bureaucratic phrasing on the English side.
This skill is content-neutral: the source can be a Markdown document, a plain article, fiction, a technical spec, a chat transcript, marketing copy, source code with comments — anything written in Russian that needs to become English.
Strict Rules
1. Preserve structure and non-prose elements byte-for-byte
Whatever non-prose elements appear in the source must survive translation byte-for-byte. Common categories — apply only those that are present in the source:
- Section markers / headings (Markdown
#, RST===, HTML<h1>, plain1./2.numbering, etc.) — translate the heading text, but keep the marker, level, and order. - Code blocks in any format (fenced
```, indented,<pre>, etc.) — keep contents EXACTLY as-is. Do not translate code, identifiers, or comments inside code unless the user explicitly asks. - Inline code / identifiers in backticks or tags (
like_this,<code>like_this</code>) — never rephrase identifier names. - Links and URLs (
[text](url),<a href>, plain URLs) — keep targets intact. Translate only the visible link text. - Markup tags: HTML, XML, frontmatter (YAML/TOML), JSX — leave the structure untouched, translate only the human-readable text inside.
- Tables: same row count, column count, and cell alignment.
- List structure: same number of items, same nesting depth, same order.
- Emphasis markers on key terms (
**bold**,*italic*,<strong>,<em>) — keep both the markers and the term they emphasize. - Numbers, version strings, dates, timestamps, units, identifiers — exactly as they appear.
- Emojis and special characters (❌, ✅, →, em-dashes) — keep in the same positions.
- Placeholder tokens (
{username},%s,%d,{{var}}) — keep exactly as-is, and position them so the English sentence reads grammatically around them.
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 dcee3a77e4ea
- 4d ago Changed · +1 lines 7c69081a1be6
- 6d ago Changed · -50 tokens per session 66de1b71aa25
- 12d ago First seen · 162 lines · 141 tokens per session scan A 9618f08b24f6
awesome-translate-ru-en is a skill published in the GitHub repository khasky/awesome-agent-skills (8 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 2,568 once invoked, about $0.0005 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.
i18n-setup
Takes a project from hardcoded strings to internationalized, connected to Crowdin, and translating continuously. Use when someone wants to add i18n or multi-language support, internationalize an app, extract hardcoded strings, set up Lingui (or another i18n library), or connect Crowdin to a repository - including…
github-action
Sets up and debugs the Crowdin GitHub Action (crowdin/github-action), which syncs a repository with a Crowdin project and opens the translation pull request. Use whenever the user wires Crowdin into GitHub Actions, writes or reviews a .github/workflows/crowdin.yml step, tunes its inputs (uploadsources…
crowdin-cli
Guides correct usage of Crowdin CLI - the crowdin command that syncs localization files between a local project and Crowdin. Use whenever the user runs, scripts, or debugs crowdin commands, creates or edits a crowdin.yml configuration, uploads sources, downloads translations, checks translation status, auto-translates…
glossary-generation
Generates a starting glossary for a Crowdin project from the project's own source strings and uploads it with the Crowdin CLI. Use when someone wants to create a glossary, extract key terms or terminology from an app's strings, mark product and feature names as do-not-translate, or seed a Crowdin project with…
context-extraction
Writes meaningful aicontext values in Crowdin JSONL files for strings that need translator context. Use when extracting context, filling aicontext fields, adding context to ambiguous strings, or working with Crowdin JSONL context files.