omh-localization-review

omh-localization-review is a skill for Claude Code, Codex from rlaope/oh-my-hermes. It costs 56 tokens per session (1,222 once invoked), scanned A, original, MIT.

A workflow for reviewing translations for terminology, context, cultural fit, and locale quality before release. Localization means adapting product text for a specific language and region.

In plain words
What is it for?
Use it to prepare a translation review brief, glossary decisions, issue lists, and quality checks for a locale such as Korean.
Why use it?
It helps identify wording inconsistencies, missing context, and cultural problems before translated content is published. It is a review process, not a publishing or visual-testing workflow.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it to prepare a translation review brief, glossary decisions, issue lists, and quality checks for a locale such as Korean.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/rlaope/oh-my-hermes/omh-localization-review
About the project

oh-my-hermes is an operating layer for Hermes Agent that organizes requests into workflows for planning, research, creation, coding handoffs, operations, and project memory. Hermes users run these workflows through the desktop app, CLI, or messenger app, while the catalogue add-ons extend its native capabilities.

rlaope/oh-my-hermes · 1,677 stars · on GitHub · rlaope.github.io

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.

Any agent
npx skills add rlaope/oh-my-hermes --skill omh-localization-review
Clone the repo
git clone --depth 1 https://github.com/rlaope/oh-my-hermes

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for omh-localization-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-localization-review/github.svg)](https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-localization-review)
Your own site
<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-localization-review"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-localization-review/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.

agentmods 80×15 button for omh-localization-review

Your own site · 80×15
<a href="https://agentmods.dev/skills/rlaope/oh-my-hermes/omh-localization-review"><img src="https://agentmods.dev/badge/skills/rlaope/oh-my-hermes/omh-localization-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 56 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,222 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.1 $0.00056 $0.01222
Opus 5 $0.00028 $0.00611
Sonnet 5 $0.00011 $0.00244
Haiku 4.5 $0.00006 $0.00122

Measured 6d ago against content hash 98e433e1d6d3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

omh-localization-review 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 6d 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.

skills/omh-localization-review/SKILL.md · 126 lines

How it starts

The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Localization Review

This is a Hermes-native localization-review workflow skill.

Why This Exists

localization-review makes terminology, context, cultural fit, and locale QA reviewable without treating a drafted translation as a published or visually validated release.

Do Not Use When

  • The request is a short sentence or word translation or rewrite with no product or locale QA context; answer directly or use content-operator.
  • The user needs fresh rendered UI evidence, clipping checks, or a visual PASS/REVISE/BLOCK verdict; use visual-qa.
  • The user asks to edit locale files, push a translation-management-system job, publish strings, or configure localization settings; use workspace-file-operator or connector-operator with explicit target and authority.
  • The request asks for a regulatory or contractual conclusion about translated legal text; use legal-compliance-review.

Examples

Good example:

  • Prompt: Review our Korean checkout strings for terminology consistency, cultural fit, and context gaps before launch.
  • Expected behavior: Prepare the locale and source-version brief, glossary choices, issue matrix, and locale QA criteria.
  • Why: The product-release context needs localization review beyond a one-off translation.

Bad example:

  • Prompt: Translate 'Your trial ends tomorrow' into Korean.
  • Expected behavior: Answer directly or route to content-operator, not localization-review.
  • Why: A one-off sentence has no product locale QA or release-review objective.

Completion Checklist

  • Findings or no-issue results are grounded in concrete file, artifact, command, or source evidence.
  • Open questions, residual risk, and missing verification are named.
  • Fixes or follow-up work are separate handoffs unless the user explicitly asked to implement them.

Recovery Notes

  • If the reviewed target is missing, inspect the requested artifact or ask one target question.
  • If independent verification is unavailable, report the gap and avoid an approval-style claim.

Read the full file on GitHub · 126 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. 6d ago Changed 98e433e1d6d3
  2. 9d ago Changed c32ec2966331
  3. 13d ago First seen · 126 lines · 56 tokens per session scan A 622c439eb339

Subscribe to this mod's changes

omh-localization-review is a skill published in the GitHub repository rlaope/oh-my-hermes (1,677 stars, last pushed today), licensed MIT. It adds 56 tokens to every session and 1,222 once invoked, about $0.0003 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.

Related

Other skills, from other repositories