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 EthanYoQ/Skill-hub --skill yq-translate-docsgit clone --depth 1 https://github.com/EthanYoQ/Skill-hubWrote 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/ethanyoq/skill-hub/yq-translate-docs)<a href="https://agentmods.dev/skills/ethanyoq/skill-hub/yq-translate-docs"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/yq-translate-docs/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/ethanyoq/skill-hub/yq-translate-docs"><img src="https://agentmods.dev/badge/skills/ethanyoq/skill-hub/yq-translate-docs.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.00025 | $0.00927 |
| Opus 5 | $0.00013 | $0.00464 |
| Sonnet 5 | $0.00005 | $0.00185 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
yq-translate-docs 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 8d 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Translate Bilingual Docs
Keep an English and Chinese document pair equivalent without forcing either language into the other's sentence structure. Use the repository's own localization contract; do not import another project's filenames, sidecars, manifests, or validation rules.
This skill is explicit-only. Use it when the user invokes $yq-translate-docs to translate, synchronize, reconcile, rename, or audit bilingual documentation. It covers maintained documentation such as READMEs, guides, release notes, and website pages. Source-code locale dictionaries follow the project's application-i18n workflow unless the user includes them.
While this explicitly invoked workflow is active, apply $yq-technical-writing to both languages so every source proposition survives in natural prose. Before a user-authorized push or readiness claim, invoke $yq-pre-push-checks once for the outgoing change set; do not run it per document or infer permission to commit or push.
Discover the pair contract
Before editing, read the applicable repository instructions and determine:
- the default document, its counterpart, and any legacy alias or redirect;
- whether either side is generated, frozen, or owned by another source;
- the glossary, terminology table, style sample, link policy, and locale-specific assets already used by the project;
- existing localization, link, rendering, or documentation checks.
Either language may be the authored side for a change. Product facts come from current code, configuration, release evidence, or another declared owner; neither language automatically overrides those sources.
Classify the change
- Update: one side changed. Translate only the changed semantic units and preserve reviewed wording outside that diff.
- New pair: no counterpart exists. Translate the whole document in sections, keeping the source structure visible as work progresses.
- Both sides changed: compare both sides with their common base and reconcile each changed unit. Preserve independent valid updates instead of choosing one language for the whole file.
- Rename or delete: move or remove the counterpart and repair navigation, language switches, and inbound links according to repository policy.
- Alias or redirect: preserve its routing role. Do not expand a deliberate compatibility stub into a second maintained translation.
What ships with it
1 file 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.
- 8d ago First seen · 60 lines · 25 tokens per session scan A 22c2ff753f00
yq-translate-docs is a skill published in the GitHub repository EthanYoQ/Skill-hub (9 stars, last pushed 5d ago), licensed MIT. It adds 25 tokens to every session and 927 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-09-04.
Other skills, from other repositories
asc-localize-metadata
Automatically translate and sync App Store metadata (description, keywords, what's new, subtitle) to multiple languages using LLM translation and asc CLI. Use when asked to localize an app's App Store listing, translate app descriptions, or add new languages to App Store Connect.
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.
asc-metadata-sync
Sync, validate, and apply App Store metadata with the current asc canonical metadata workflow. Use when updating metadata, localizations, keywords, or migrating legacy fastlane metadata.
asc-whats-new-writer
Generate engaging, localized App Store release notes (What's New) from git log, bullet points, or free text using canonical metadata under ./metadata. Optionally pairs with promotional text updates.
vs-item-onboarding
Match the language of the user's most recent message in every line of prose you write — confirmation prompts, status notes, hand-off summaries, questions, error explanations, and any internal thinking / reasoning / planning output that the host may surface (e.g. blocks, "thinking" panels, scratchpad notes, todo…
shogun-readme-sync
A skill that compares an English README with its Japanese counterpart and brings them back into alignment. A README is the project document that explains what the software is and how to use it.