translate

A command for keeping Korean and Japanese copies of a README, a project’s main documentation file, aligned with the English version. It can translate the whole file or update only sections that changed.

In plain words
What is it for?
Use it to synchronise README.md with README.ko.md and README.ja.md, either after small edits or after major changes to the document.
Why use it?
It removes the manual work of finding new, edited, or deleted documentation in multiple language files. It also helps preserve links, code examples, tables, and Markdown formatting.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/roboco-io/awesome-vibecoding/translate
Clone the repo
git clone --depth 1 https://github.com/roboco-io/awesome-vibecoding

Made for: Claude Code.

Per session 23 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 558 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00023 $0.00558
Opus 5 $0.00012 $0.00279
Sonnet 5 $0.00005 $0.00112
Haiku 4.5 $0.00002 $0.00056

Measured 2d ago against content hash a3e1da1a5129, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

.claude/commands/translate.md · 68 lines

How it starts

The opening of the file, as written. The whole thing — 68 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

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:

  1. Reads both README.md and the target language file (README.ko.md or README.ja.md)
  2. Identifies new or modified items in README.md
  3. Locates the corresponding section/position in the target file
  4. Translates new items and inserts them at the exact same position
  5. Removes deleted items from the target file if any

Full Translation Process

Each agent:

  1. Reads README.md
  2. Translates the entire content to the target language
  3. Saves the translated file

Position Sync Example

When new item added to README.md:

### Cloud & Platform Integrations
| Tool | Description |
|------|-------------|
| [**Lovable**](https://lovable.dev/) | Full-stack app generation with Supabase |
| [**NewTool**](https://newtool.com/) | New AI tool description |
| [**Duet AI**](https://workspace.google.com/solutions/ai/) | Google Workspace AI integration |

→ Insert translated item at the same position (between Lovable and Duet AI) in README.ko.md and README.ja.md

Read the full file on GitHub · 68 lines

Changes

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.

  1. 2d ago First seen · 68 lines · 23 tokens per session scan A a3e1da1a5129

Subscribe to this mod's changes

translate is a command published in the GitHub repository roboco-io/awesome-vibecoding (201 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 23 tokens to every session and 558 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.