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 mtarcure/claude-vibe-squad --skill locale-adaptationgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/locale-adaptation)<a href="https://agentmods.dev/skills/mtarcure/claude-vibe-squad/locale-adaptation"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/locale-adaptation/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/mtarcure/claude-vibe-squad/locale-adaptation"><img src="https://agentmods.dev/badge/skills/mtarcure/claude-vibe-squad/locale-adaptation.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.00054 | $0.00252 |
| Opus 5.5 | $0.00022 | $0.00101 |
| Sonnet 5.5 | $0.00011 | $0.00050 |
| Haiku 4.5 | $0.00005 | $0.00025 |
Grade A, and why
locale-adaptation 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 1mo 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.
What it actually says
Locale Adaptation
Adapt content for a target locale by meaning and tone — idiom, dialect, register, cultural fit — not literal translation.
Steps
- Read the source intent and tone before translating a word.
- Adapt idiom, register, and cultural references to the target locale; preserve meaning over literal wording.
- Annotate every place a literal rendering would mislead or offend.
- Honor the glossary / do-not-translate list supplied with the task; when none is supplied, extract the candidate terms and confirm them before translating.
- If a source claim or campaign cannot carry over without changing its meaning, surface options to the operator rather than silently altering it.
Acceptance
- Meaning and tone are preserved; cultural mismatches are annotated.
- Glossary and do-not-translate terms are respected.
- Back-translation is used only as a diagnostic, never as proof of correctness.
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.
- 1mo ago First seen · 22 lines · 54 tokens per session scan A 8b89cd182d91
locale-adaptation is a skill published in the GitHub repository mtarcure/claude-vibe-squad (164 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 252 once invoked, about $0.0002 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 skills, from other repositories
gh-find-prs
Survey open Codewhale PRs and triage each for mergeability and disposition against the real landing branch.
codew-release-qa-sweep
Use before claiming Codewhale release work is done: run the full gate sweep and list the manual QA targets.
gh-file-issue
Use when filing a new Codewhale GitHub issue: turn a bug or idea into a well-formed, actionable issue with repro, acceptance criteria, labels, and milestone.
gh-treasure-hunt
Hunt the issue/PR queue for highest value-over-risk wins: clean focused community PRs, already-implemented issues to close, safe quick-fixes.
plan
Turn a sufficiently understood task into an ordered implementation plan with dependencies and verification. Orchestrate Codewhale’s native plan state; do not build a parallel planner.
document
Skill "document" from Hmbown/Codewhale, covering document, when to use, non-goals and workflow.