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.
git clone --depth 1 https://github.com/roboco-io/awesome-vibecodingWrote 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/commands/roboco-io/awesome-vibecoding/translate)<a href="https://agentmods.dev/commands/roboco-io/awesome-vibecoding/translate"><img src="https://agentmods.dev/badge/commands/roboco-io/awesome-vibecoding/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/commands/roboco-io/awesome-vibecoding/translate"><img src="https://agentmods.dev/badge/commands/roboco-io/awesome-vibecoding/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.00023 | $0.00628 |
| Opus 5.5 | $0.00009 | $0.00251 |
| Sonnet 5.5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00002 | $0.00063 |
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 29d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Modes
1. Full Translation
Retranslate the entire README.md. Use when structure has significantly changed.
2. Incremental Sync (Default)
Find added/modified/deleted items in README.md and apply them to the same positions in Korean/Japanese files.
Translation Guidelines
Common Rules
- Keep technical terms, product names, code, and URLs in English
- Preserve markdown formatting, links, and code blocks exactly
- Maintain table structure precisely
- Preserve all explicit anchor IDs and HTML comments, including catalog boundaries and recent-updates markers
- Keep four-column resource tables, verification dates, and source ordering identical across languages
Korean (README.ko.md)
- First line:
# Awesome Vibe Coding (한국어) - Keep language selection links:
*Language: [English](README.md) | [한국어](README.ko.md) | [日本語](README.ja.md)* - Add space after bold text when followed by Korean characters (e.g.,
**텍스트** 다음)
Japanese (README.ja.md)
- First line:
# Awesome Vibe Coding (日本語) - Keep language selection links
Execution
Use the Task tool to run two translation agents in parallel:
- Agent 1: README.md → README.ko.md (Korean)
- Agent 2: README.md → README.ja.md (Japanese)
Incremental Sync Process (Default)
Each agent:
- Reads both README.md and the target language file (README.ko.md or README.ja.md)
- Identifies new or modified items in README.md
- Locates the corresponding section/position in the target file
- Translates new items and inserts them at the exact same position
- Removes deleted items from the target file if any
Full Translation Process
Each agent:
- Reads README.md
- Translates the entire content to the target language
- Saves the translated file
Position Sync Example
When new item added to README.md:
### App & UI Prototyping
| Resource | When to use it | Access / terms | Verified |
|---|---|---|---|
| [**Lovable**](https://lovable.dev/) | Generate an app prototype | Check terms | — |
| [**NewTool**](https://newtool.com/) | New AI tool description | Check terms | — |
| [**Replit**](https://replit.com/) | Build in a browser workspace | Check terms | — |
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.
- 29d ago Changed · +2 lines 177341abbc9f
- 1mo ago First seen · 68 lines · 23 tokens per session scan A a3e1da1a5129
translate is a command published in the GitHub repository roboco-io/awesome-vibecoding (215 stars, last pushed 7d ago), licensed CC0-1.0. It adds 23 tokens to every session and 628 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-08-30.
Other commands, from other repositories
translation-review
A command for systematically reviewing translated project files against the original version, including focused checks, quality scoring, and release verification.
translate-docs
Translate CodexSpec repository READMEs or site documentation with shared terminology and fidelity checks.
growth-localization
Localization strategy and international expansion.
brand-update
Recalibrate the brand pack after positioning, personas, pricing or naming changed — propagate the change through terminology, strings and every locale in the same edit.
plan-localization
Plan localisation covering extraction, translation workflow, and the layout and format issues that follow.
export
A command that exports completed translation data into a finished EPUB or TXT file.