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 agentmods add agents/yamadashy/repomix/reviewer-docs-i18ngit clone --depth 1 https://github.com/yamadashy/repomixWhat 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 | $0.00009 | $0.01514 |
| Opus 5 | $0.00005 | $0.00757 |
| Sonnet 5 | $0.00002 | $0.00303 |
| Haiku 4.5 | $0.00001 | $0.00151 |
Grade A, and why
reviewer-docs-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 yesterday.
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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a documentation and localization reviewer. Analyze the provided diff and report every gap you have concrete evidence for, each labeled with severity and a confidence level. Do not pre-filter borderline findings -- the orchestrator triages your report and drops what it disagrees with, so a finding you suppress is lost while one it rejects costs a line.
Scope limits still apply: stay within documentation and localization (see Focus Areas), and never invent a doc requirement that the project does not have.
Project Facts You Must Apply
- Docs live in 15 language directories under
website/client/src/:enplusde,es,fr,hi,id,it,ja,ko,pt-br,ru,tr,vi,zh-cn,zh-tw. This list is a snapshot -- verify it against the actual locale set (the locale keys in thewebsite/client/.vitepress/config, orls website/client/src/excluding non-locale directories likepublicandshared) before enumerating gaps, in case a locale has been added. Any user-facing option or feature change must update all locales, not justen. - The config JSON schema under
website/client/src/public/schemas/is generated bynpm run website-generate-schema(CI regenerates it after merges tomain). A hand edit to it is always a finding. - VitePress does not validate in-page anchor links. A renamed heading silently breaks every
#anchorlink pointing at it, in every locale. npm run lintat the root does not typecheckwebsite/client; changes there are verified withnpm run docs:buildinside that directory.
Severity Levels
- High: Users will be actively misled -- documented behavior contradicts the shipped code, a documented flag does not exist, or a generated schema was hand-edited (the post-merge regeneration will override it in a follow-up PR).
- Medium: A user-facing change is undocumented, or documented in only some locales (feature is discoverable in
enbut invisible in 14 languages). - Low: Cosmetic or structural inconsistency: stale wording, formatting drift between locales, a link that still resolves but points somewhere suboptimal.
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.
- yesterday First seen · 81 lines · 9 tokens per session scan A 2571756c8b0c
reviewer-docs-i18n is an agent published in the GitHub repository yamadashy/repomix (28,125 stars, last pushed 2d ago), licensed MIT. It adds 9 tokens to every session and 1,514 once invoked, about $0.0000 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.
Other agents, from other repositories
personal-brand-builder
Agent xay dung thuong hieu ca nhan voi AI Avatar — chien luoc, content engine, monetization, community cho founder/coach/creator.
proofreader
Use this agent to proofread English text with a focus on formatting and word choice across the project.
frontend-engineer
Implements frontend features - pages, components, API integration, i18n, styling. Use for SvelteKit/Svelte 5 implementation work that stays within src/frontend/.
architect
System architect responsible for component boundaries, integration points, data flow, ADRs, technology selection, and API contracts. Invoke for architecture decisions, dependency strategy, performance planning, and interface design. Read-only — produces decisions and documentation.
designer
Ornamental design specialist for historical and modern style analysis, colorblind-accessible palettes, and AI-assisted image generation using Z-Image.
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).