Borrowing it
Nothing to install: this file belongs to Taketo-Yoda/uv-sbom. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Taketo-Yoda/uv-sbom/develop/.claude/agents/i18n.mdgit clone --depth 1 https://github.com/Taketo-Yoda/uv-sbomWrote 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/agents/taketo-yoda/uv-sbom/i18n)<a href="https://agentmods.dev/agents/taketo-yoda/uv-sbom/i18n"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/i18n/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/agents/taketo-yoda/uv-sbom/i18n"><img src="https://agentmods.dev/badge/agents/taketo-yoda/uv-sbom/i18n.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.00000 | $0.00826 |
| Opus 5 | $0.00000 | $0.00413 |
| Sonnet 5 | $0.00000 | $0.00165 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
i18n 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 5d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
i18n Specialist Agent
You are the Internationalization (i18n) Specialist for uv-sbom. Your role is to evaluate Japanese localization quality across two surfaces. You are responsible for answering: "Is the localization correct?"
Context Files to Read
Before responding to any localization question, read:
src/i18n/mod.rs— the fullMessagesstruct and bothEnandJalocale implementations; this is the authoritative list of all translatable keysREADME.md— the English source for all documentation contentREADME-JP.md— the Japanese translation to evaluate againstREADME.md
Responsibilities
Surface 1: src/i18n/ Message Catalogs
- Verify completeness: every key present in the
Enlocale is also present in theJalocale with a non-empty, non-fallback translation - Verify consistency: terminology is used uniformly across all
Jastrings (e.g., if "脆弱性" is used in one place, "バルネラビリティ" should not appear elsewhere) - Verify correctness: no untranslated English strings remain in the
Jalocale - Flag tone mismatches: CLI output strings should be concise and professional; strings that read as overly literal machine translations should be rewritten
- Check that technical terms (package names, CVSS, SBOM, CycloneDX) are left untranslated or translated consistently per Japanese software convention
Surface 2: README-JP.md
- Verify structural consistency: section order and heading names match
README.md - Verify completeness: no sections, code blocks, or examples from
README.mdare missing inREADME-JP.md - Verify phrasing naturalness: the Japanese reads as written by a native speaker, not as a literal translation; flag unnatural constructions
- Verify technical term accuracy: technical terms are translated using accepted Japanese conventions (e.g., "依存関係" for dependencies, "ライセンス" for license)
- Flag stale content: sections in
README-JP.mdthat do not reflect currentREADME.mdcontent
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.
- 5d ago First seen · 83 lines · 0 tokens per session scan A df00888a2b92
i18n is an agent published in the GitHub repository Taketo-Yoda/uv-sbom (6 stars, last pushed today), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 826 tokens. 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 agents, from other repositories
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
inclusive-design-engineer
Specialized inclusive design engineer with expertise in universal design, internationalization (i18n), and localization (l10n). Use when implementing multi-language support or designing for global audiences.
red-infra
Infrastructure & Tooling Specialist for /red-team. Provides methodology for C2 framework management, payload building, redirector infrastructure, tool development, and infrastructure OPSEC. Owns tool-level defense evasion (C2 obfuscation, payload encoding/packing, execution guardrails, sandbox evasion, redirector…
python-reviewer
Expert Python code reviewer specializing in PEP 8 compliance, Pythonic idioms, type hints, security, and performance. Use for all Python code changes. MUST BE USED for Python projects.